What does an eval score actually claim about my agent?

An eval score is a claim about the eval set, not about the agent. A high pass rate means most of the traces your graders ran on passed the specific checks those graders make, and nothing more. It says nothing about a failure mode none of your graders look for, and nothing about traffic your eval set doesn’t cover: a new user segment, a tool that just shipped, a prompt injection nobody’s tried yet.

Widening scope only helps up to a point. A grader tied to one specific behavior tells you exactly what broke when it fails. A single “overall quality” grader can pass while a real failure slips through underneath it, because meeting a broad standard says less about any one thing than a narrow check does.

Read a score as coverage of what you checked, not as a verdict on the agent.

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