Why does grading each agent separately miss multi-agent failures?

Because the failure often lives in what one agent’s message to another does or doesn’t carry, and each agent’s own output can look correct when graded alone. MAST’s own trace data shows this directly: a Phone Agent calls a login API with the credentials it was given, gets “invalid credentials” back, and reports that accurately to the Supervisor Agent, without saying the username field needs a phone number. Read either agent’s turn on its own and it looks reasonable: the Phone Agent described what actually happened, and the Supervisor Agent asked a sensible follow-up given what it knew. The login keeps failing anyway, because the one fact that would have fixed it never crossed the handoff.

That’s why inter-agent misalignment, 36.9% of the paper’s annotated failures, is defined at the boundary between agents rather than inside any single agent’s output. MAST classifies the trace, not the answer, because a grader scoring one agent’s final response on its own never sees the message that didn’t get passed.

sources

keep reading

More on this.

Two ways to run Tessary.

Tessary is an open-source agent reliability platform. Cloud and self-hosted run the same workflow on the OpenTelemetry traces your agent already emits.

Tessary Cloud

We host it for you. Send your first trace with nothing to deploy and no model key.

what's includedper organization
traces
10,000 per calendar month
stored trace data
1 GB
retention
30 days
model credit
$10, one-time, for triage and root-cause analysis
credit card
not required

Self-hosted Tessary

Run the open-source code on your own infrastructure with one command. Add your own model key for triage and root-cause analysis.

Self-host Tessary for me by following https://github.com/tessaryai/tessary/blob/main/setup.md

docker compose -f oci://docker.io/tessaryai/tessary:compose up -d -y