Executive Summary

To evaluate an AI agent that works by calling tools, you need a test. But real production data is sensitive and scarce, so the field is moving toward building those tests out of synthetic data. The problem is that no one grades whether the test itself actually resembles the real world. This piece looks at SynAE (arXiv 2605.22564, research from Carnegie Mellon University and Microsoft), a framework aimed squarely at that gap.

One case SynAE surfaces makes that gap concrete. Build the same test with a standard synthetic-data tool (NVIDIA NeMo) but swap the backend model, and the validity scores stay almost identical at 0.98 and 0.99 while fidelity splits wide open at 0.71 and 0.94. Look at validity alone and the two tests seem equally good, yet how well they reproduce reality is entirely different. This is exactly why the researchers insist that no single metric can define the quality of synthetic data.

For readers who diagnose data for a living, that conclusion translates into a question one layer deeper. To trust a model's score, you first have to diagnose the data that becomes the test that produced it.

0.71 vs 0.94

Fidelity of the two backends

Same NeMo tool, split by Llama3.1-8B vs. GPT-4o-mini

0.98 vs 0.99

Validity of the two backends

Nearly identical — validity alone can't tell them apart

≈1.0 → 0

Blank Filling's KNN-precision

Push masking to the max and fidelity collapses while diversity actually rises

1

Doubt the Test First

Tool-calling agents are usually evaluated on execution traces: a static dataset holding the user's instructions, the agent's responses, and the tool calls exchanged in between serves as the test to grade against. But real production data is hard to use as a test. It holds sensitive or proprietary information, and there is rarely enough of it to support comprehensive pre-deployment testing. So the practice of replacing or augmenting real data with synthetic data to build evaluation benchmarks has taken hold.

That is where the core difficulty arises. How do you confirm, in numbers, the relationship between this synthetic data and the real data it stands in for? SynAE is a framework built to answer exactly that question. It looks at synthetic data across four axes: task instructions and intermediate responses, tool calls, final output, and the downstream performance you observe when you actually grade agents with the test.

Each axis is then measured on three properties. Validity asks whether the synthesized instruction-response plausibly accomplishes the task goal; fidelity asks how faithfully it reproduces the distributions and patterns of the real data; diversity asks how wide a range it covers. Validity answers "does this make sense," fidelity answers "does this resemble reality," and diversity answers "is this wide enough."

The four axes that measure a synthetic test Task instructions ·intermediate responses Tool calls Final output Downstream performance each axis graded on three properties Validity does it make sense Fidelity does it resemble reality Diversity is it wide enough Four axes × three properties — the score of any one cell cannot define the quality of the whole test

▲ Original Pebblous diagram (reconstruction of the SynAE evaluation structure)

2

Where a Single Metric Breaks

The researchers deliberately injected representative synthetic-data generation methods to see what SynAE would catch. What stands out most is that two generation methods move in opposite directions. Blank Filling masks some of the original tokens and lets the model fill them in; as the masking ratio climbs, it drops fidelity but actually raises diversity. Oversampling does the reverse. It duplicates a sequence to inflate the set, and as the duplication ratio climbs, fidelity and diversity collapse together.

In other words, even within the same "synthetic data generation," two properties can move in the same direction or in opposite ones depending on the method. If you take diversity alone as your standard for a good test, you will catch Oversampling's diversity collapse but wave Blank Filling's fidelity collapse right through. One metric cannot see where the other one breaks.

Blank Filling Oversampling Fidelity Diversity Fidelity Diversity Fidelity↓ · Diversity↑ (moving apart) Fidelity↓ · Diversity↓ (collapsing together)

▲ Original Pebblous diagram (reconstruction of SynAE's per-method trade-offs)

The divergence does not appear only between different properties. Even within fidelity, the individual metrics disagree. In-Context Generation produces new data from a few examples, and as the example count grew it improved one fidelity metric (KNN-precision) while another (KNN-recall) got worse. "Fidelity is high" cannot be lumped into one phrase; the conclusion flips depending on which metric you looked at.

What it concretely looks like for a synthetic test to drift away from reality shows up in a case SynAE caught. Swap the original data's "recommend art landmarks" task for "sports landmarks" to boost diversity cheaply, and the surface form stays intact while the instruction, the tool calls, and the final output no longer line up—so the task itself fails to hold together. You cannot spot that mismatch from the surface of the test; only measuring several properties together brings it out.

The NeMo case from the Executive Summary captures the whole story. The validity of two tests built with the same tool is effectively equal at 0.98 and 0.99, yet fidelity splits to 0.71 and 0.94. Had you measured only validity and moved on, you would have missed that the test built with GPT-4o-mini is far closer to real production patterns.

3

The Paradox of Stable Rankings

SynAE's fourth axis, downstream performance, produces an intriguing paradox. Even when you push Blank Filling's masking high enough to wreck the tool-call metrics, the ranking you get by grading several models with that test barely moves. Because a high-performing model still outperforms a low-performing one even when tool-use patterns are distorted, the relative ordering among models holds.

That result reveals that two questions are, in fact, different questions. "Can this test rank the models?" and "Does this test faithfully resemble the real world?" are separate, and they yield separate answers. A test that is flawless for ranking can be a failing grade on the standard of reproducing reality. The reverse holds too.

Ranking stability and reality reproduction are different axes Downstream ranking stability → Fidelity → Unstable ranking · faithful to reality Ideal point Both weak Ranking stable · fidelity fails Blank Filling (masking↑)

▲ Original Pebblous diagram (reconstruction of SynAE's ranking-fidelity paradox)

So "our model came in Nth on this benchmark" and "this benchmark reproduces our reality" do not vouch for each other. The fact that a ranking is stable does not prove the fidelity of the test. That is precisely why the two have to be measured separately.

4

Diagnose the Test

This blog recently covered a benchmark that grades data-analysis agents skill by skill (cleaning, joining, anomaly detection), arguing that a single total score erases an agent's strengths and weaknesses, so the grading rubric should be broken into finer pieces. SynAE aims one layer deeper. No matter how finely you break the rubric, if the test data it stands on is flimsy, that fineness becomes an illusion. The question underneath remains: how faithfully, and how widely, does the skill-labeled task data itself capture reality?

It is a different register from the recent piece on coding agents and scientific reproduction. That piece asked a question about capability: why the agent can't solve the problem. This one asks a question about the evaluation tool, whether the test that posed the problem resembles the real world at all. The first question faces the model; the second faces the data.

Diagnosing data quality has always been treated as a multidimensional problem. That you must weigh several yardsticks together (accuracy, completeness, consistency) is a principle data-quality research has long emphasized. What SynAE newly did is apply that multidimensionality to a concrete and urgent case: the synthetic tests used to evaluate agents. Requiring that validity, fidelity, and diversity be viewed together across four axes is the latest edition of the old principle that data quality must not be compressed into a single number.

So the first question an organization considering a synthetic benchmark should ask changes. Not "what score does our model get on this benchmark," but first: is this benchmark's test valid, does it faithfully reproduce our reality, is it diverse enough? Trusting a model's score begins with diagnosing the test.

Editor's Note. The concern Pebblous has returned to again and again points at the same place. Whether data is AI-Ready is decided not by swapping models but by checking several yardsticks together: validity, fidelity, and diversity. SynAE is a case of applying that check to an agent's test, and a starting thread for moving the language of trusting a benchmark from the score to the diagnosis of the data.

R

References