SYNTHESIS NOTE
Agentic Systems and Tool Use Reasoning, Retrieval, and Evaluation

Can agents evaluate AI outputs more reliably than language models?

Does active evidence collection through tool use reduce judge inconsistency compared to passive reading-based evaluation? This matters for benchmarking AI systems where evaluation reliability directly affects research validity.

Synthesis note · 2026-02-23 · sourced from Agents Multi
What makes multi-agent teams actually perform better? Do reasoning traces show how models actually think?

LLM-as-a-Judge evaluates outputs by reading them and scoring. Agent-as-a-Judge evaluates by actively investigating — collecting dynamic evidence through tool use before making judgments. The difference in reliability is dramatic: on complex software engineering tasks with dependencies between requirements, Agent-as-a-Judge shows a judge shift of 0.27% from human consensus while LLM-as-a-Judge reaches 31.24%.

The architecture has eight modular components: (1) a graph module capturing project structure and dependencies, (2) a locate module identifying relevant files, (3) a read module understanding multimodal data across 33 formats, (4) a search module for contextual code understanding, (5) a retrieve module extracting information from long texts, (6) an ask module making pass/fail determinations, (7) a memory module storing historical judgments, and (8) a planning module strategizing next actions.

The design mirrors how human evaluators actually work — 58 hours of initial human evaluation followed by 28.5 additional hours of consensus-building debate. The human process itself requires investigation, not just reading. Single-pass evaluation is fundamentally inadequate for tasks where understanding requires traversing dependencies and cross-referencing evidence.

However, the memory module proved detrimental: errors in previous judgments cascade into current decisions, creating a chain of errors. Historical judgment information was supposed to help assess current requirements but instead propagated mistakes. This is a crucial design finding — agentic evaluation systems need error isolation mechanisms, not just more context.

Since Can LLM judges be fooled by fake credentials and formatting?, Agent-as-a-Judge addresses these biases structurally: the agent grounds its judgment in collected evidence rather than relying on heuristic pattern-matching. And since Can LLM judges be tricked without accessing their internals?, the agentic approach offers a path toward more robust evaluation — but only if the error cascade problem is solved.

Inquiring lines that use this note as a source 157

This note is a source for these synthesized inquiries. Follow a line forward into its question, or open it to trace back to all of its sources.

Related concepts in this collection 4

This note in its neighbourhood — explore the map, then jump to a related concept in the list below.

Concept map
16 direct connections · 127 in 2-hop network ·medium cluster Open in graph ↗

Click a node to walk · click center to open · click Open in graph to see this note in the full knowledge graph

your link semantically near linked from elsewhere

Related papers in this collection 8

Papers most semantically related to this note, ranked by cosine similarity in the embedding space.

Original note title

agent-as-a-judge with dynamic evidence collection achieves two orders of magnitude lower judge shift than LLM-as-a-judge on complex tasks