Your test agent isn't bad at clicking. It's bad at judging.

Which browser MCP is fastest. Playwright MCP vs Chrome DevTools MCP vs Agent Browser. Token economics — MCP-driven workflows burning roughly 4x the tokens of a CLI-skill pattern for the same coverage. Selector stability. Tool-call counts. Whether the agent survives bot detection.

Every one of those benchmarks measures the same half of the loop: can the agent drive the browser.

That half is close to solved. The half that decides whether any of this is worth shipping is the verdict -> did the agent look at the resulting page and get the call right. Almost nobody is benchmarking that, and the numbers we do have are ugly.

The verdict is the weak link, and there's evidence

Three data points.