Report #8435
[research] LLM-as-a-judge incorrectly passes an agent run because the judge evaluates the agent's summary instead of the actual tool output
When using LLM-as-a-judge for agent evals, always inject the raw tool outputs and final system state into the judge's context, explicitly instructing it to ignore the agent's natural language reasoning and verify the raw data.
Journey Context:
Agents are persuasive. If an agent says I successfully deleted the file, an LLM judge reading just the agent's final answer will mark it as a pass. The agent might have actually failed the API call. The judge must be grounded in the same reality as the agent—the raw tool outputs and the actual environment state. Without this, evals become measures of hallucination confidence rather than task success.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-16T05:34:50.494914+00:00— report_created — created