How to read benchmarks and leaderboards
A benchmark is a fixed test with a score. It is useful and easy to misread.
Words on this page (7)
- benchmark
- : A fixed test with a score used to compare models.
- training
- : Adjusting a model's parameters on data so its predictions improve.
- agent
- : A model run in a loop that chooses its own tools and steps until the task is done.
- harness
- : Everything around the model that makes it an agent: prompts, tools, rules, sandboxes, hooks, memory and checks.
- sampling
- : Picking the next token at random according to the model's probabilities.
- tool
- : A function the model can ask your program to run, described by a name, description and argument schema.
- rubric
- : A written list of criteria used to grade an output.
What to check
Is the test saturated, with top models all near 100 percent so differences are noise? Could the model have seen the answers in (contamination)? Does the task look like yours? Was the score measured by the vendor or independently? How many runs, and what was the spread? Human preference arenas measure style and helpfulness in chat, which is not the same as correctness on your task. for depend heavily on the used, so a score is for a model plus a harness.
How to use them
Use leaderboards to shortlist, then run your own examples. Track a small number of benchmarks that resemble your work. Be suspicious of any single headline number.
A worked example: is the gap real?
Model A scores 87.3 and model B 86.9 on a test with 500 questions. With that many questions the typical error is about 1.5 points (about 3 points at 95 percent confidence), so a gap of 0.4 is within noise. Treat them as equal until a larger or different test separates them.
How the noise estimate works
A score on n questions is a sample. The typical sampling error is sqrt(p(1 - p) / n). For p = 0.87 and n = 500 that is sqrt(0.87 × 0.13 / 500), about 0.015, or 1.5 points.
A gap between two scores is noisier than either score alone, because both carry error. Treating them as independent, the gap error is about 1.5 times the square root of 2, or about 2.1 points. About 95 percent of the time the true gap sits within roughly twice that. A 0.4 gap is far inside it. Models tested on the same questions have a tighter gap in practice, but 0.4 still tells you very little.
What goes wrong: a model that has seen the test
Contamination means test questions appeared in the training data. The symptom is a high public score that does not carry over. A model scores 90 on a famous test, then does much worse on questions you wrote in the same style.
To check, write 20 fresh questions of the same type and compare. A large drop suggests memorization. It does not prove it, since your questions may also be harder.
When a public benchmark is the wrong tool
You summarize legal contracts. A coding leaderboard tells you almost nothing about that. Build your own test:
- Collect 30 real inputs from your work.
- Write the answer you want for each, or a short (a checklist for grading).
- Run each candidate model three times on all 30.
- Record the average and the spread between runs.
If a model's three runs vary by more than the gap between models, you cannot separate them yet. Add more examples.
Common mistake
Quoting a single number without its context.
A new model tops a leaderboard by half a point. A team switches to it and finds it does worse on their documents. The leaderboard measured something real, but not their task. Benchmarks are a starting list, not a verdict.
Check yourself
All top models score 97 to 99 percent. What does that tell you?
Not quite. Small differences near the ceiling are mostly noise.
An agent benchmark score reflects what?
Not quite. Harness choices change results significantly.
Model A scores 87.3 and B scores 86.9 on 500 questions. Which conclusion is fair?
Not quite. With 500 questions, a 0.4 gap is smaller than typical sampling error.
You got 0 of 3 right.
Go deeper
- ToolLMArenaTool
LMArena · Human preference rankings.
- Tool
Artificial Analysis · Independent quality, speed and price.
- ToolSWE-benchTool
Princeton NLP · Coding agent benchmark.
- Tool
Epoch AI · Independent runs across many benchmarks.
- ArticleAI Snake OilArticle
Narayanan and Kapoor · Critical reading of AI claims.
Spotted a mistake or something unclear? Report it on GitHub.