Multi-Agent & Production
Agent Evals
11 min+120 XPStep 1/10
Outcome ≠ trajectory
A single-agent answer eval asks 'was the output right'. An agent eval must also ask 'was the path sound' — because a lucky trajectory hides a broken agent. The research agent that cited the wrong source but guessed the right answer passed your outcome eval and will fail the next hundred tasks.
Grade both layers:
- Task success — did the environment end in the correct state? For agent tasks this is often checkable in code: the file exists, the DB row is right, the test passes.
- Trajectory quality — did it get there the right way, at the right cost?
insight
Outcome-only evals overfit to luck. A 60% success rate with clean trajectories beats 70% built on flailing that happened to land.