← Latest papers
💬 NLP

Holistic Evaluation and Failure Diagnosis of AI Agents

This paper introduces a holistic evaluation framework that combines top-down diagnosis with bottom-up span-level assessment to effectively localize and categorize failures in AI agents, achieving state-of-the-art performance on TRAIL benchmarks and demonstrating that evaluation methodology, rather than model capability, is the primary bottleneck in agent diagnosis.

Original authors: Netta Madvil, Gilad Dym, Alon Mecilati, Edo Dekel, Jonatan Liberman, Rotem Brazilay, Liron Schliesser, Max Svidlo, Shai Nir, Orel Shalom, Yaron Friedman, David Connack, Amos Rimon, Philip Tannor, Shir
Published 2026-05-15
📖 5 min read🧠 Deep dive

Original authors: Netta Madvil, Gilad Dym, Alon Mecilati, Edo Dekel, Jonatan Liberman, Rotem Brazilay, Liron Schliesser, Max Svidlo, Shai Nir, Orel Shalom, Yaron Friedman, David Connack, Amos Rimon, Philip Tannor, Shir Chorev

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you hire a team of AI robots to solve a complex puzzle, like finding a specific number hidden inside a 20-minute YouTube video or fixing a broken piece of software code. Sometimes, the robots succeed. Other times, they fail.

The problem, according to this paper, is that current ways of checking their work are like a teacher who only looks at the final answer on a test. If the answer is wrong, the teacher marks it "Fail" and moves on. They don't tell you why it's wrong, or where in the 50-step process the robot got confused. Did it misread the instructions? Did it use the wrong tool? Did it just make up a number?

The authors from Deepchecks have built a new "Holistic Evaluation Framework" that acts like a super-detailed detective. Instead of just grading the final result, it breaks the robot's entire journey down into tiny, manageable steps (which they call "spans") to find exactly what went wrong.

Here is how their system works, using simple analogies:

1. The Two-Pronged Detective Approach

The authors realized that looking at a robot's work from just one angle isn't enough. They combined two different perspectives:

  • The "Bottom-Up" Detective (The Microscope):
    Imagine looking at every single tool the robot used. Did the robot ask the right question? Did the answer it got back make sense? Did it crash when trying to open a file?

    • Analogy: This is like a mechanic checking every single bolt and wire in a car engine. If one bolt is loose, they find it immediately. This is great for spotting specific mistakes, like a typo in a command or a broken tool, but it might miss the bigger picture (like the fact that the mechanic was looking at the wrong car entirely).
  • The "Top-Down" Detective (The Bird's-Eye View):
    This looks at the whole journey. Did the robot follow its own plan? Did it waste time asking the same question five times? Did it forget to check a crucial piece of information?

    • Analogy: This is like a traffic controller watching the whole flight path. They can see if the plane is taking a weird detour or wasting fuel, even if every single engine part is working perfectly.

The Magic: By using both the microscope and the bird's-eye view, the system can tell you exactly what went wrong (e.g., "Hallucination") and where it happened (e.g., "Step 14, when asking the search tool").

2. Why Old Methods Failed

The paper tested their new system against older methods using a tough test called the TRAIL benchmark (which uses real-world tasks like finding data or fixing code).

  • The "Monolithic Judge" (The Old Way):
    Imagine asking a single, very smart human to read a 100-page report and find every mistake in one go.

    • The Problem: As the report gets longer, the human gets overwhelmed. They might miss the mistake on page 45 because they are focused on page 100. In the paper, even the smartest AI models (like GPT-5.4) failed miserably at finding specific errors in long, complex tasks when asked to do it all at once. They could guess what kind of error happened, but they couldn't point to where it was.
  • The "New Framework" (The Smart Way):
    Instead of one person reading the whole book, imagine a team of specialists. One person checks page 1, another checks page 2, and so on. Then, a manager combines their notes.

    • The Result: The system didn't get overwhelmed, even when the tasks were very long. It found errors with much higher accuracy.

3. The Results: A Massive Win

When they compared their new system to the best existing methods:

  • Finding the "Where": Their system was 3.5 times better at pinpointing exactly which step failed. On the hardest tests, it was 12.5 times better at finding both the error type and its location simultaneously.
  • The "Same Brain, Better Method" Surprise: They used the exact same super-smart AI model (GPT-5.4) for both the old way and the new way.
    • Old Way: The AI got 7% accuracy on finding errors in long code tasks.
    • New Way: The same AI got 86% accuracy.
    • Conclusion: The problem wasn't that the AI wasn't smart enough; the problem was that the method of asking it to judge the work was broken. Changing the method unlocked the AI's true potential.

4. What This Means (According to the Paper)

The paper concludes that to fix AI agents, we need to stop just looking at the final score. We need a system that breaks the work down into small, independent chunks to diagnose failures precisely.

They also noted that the test data they used (TRAIL) had some messy labeling (like humans marking the wrong step as the error), but even with those imperfections, their new method still crushed the competition.

In short: The paper argues that we don't need "smarter" AI to evaluate AI agents; we need a smarter way to evaluate them. By breaking big problems into small, manageable pieces, their system finds errors that other methods completely miss.

Drowning in papers in your field?

Get daily digests of the most novel papers matching your research keywords — with technical summaries, in your language.

Try Digest →