npx tsx benchmarks/run-benchmarks.ts --suite comparison. Full raw results and methodology live in benchmarks/ on GitHub. This page is a summary, not the methodology document.
Orientation cost
What an agent pays to “see” a page on arrival. A Charlottenavigate returns a usable orientation by default. That orientation includes landmarks, headings, and interactive element counts grouped by page region. The Playwright MCP equivalent is browser_snapshot, which returns the full accessibility tree. browser_navigate alone returns only a short confirmation, not page content, so it isn’t a like-for-like comparison.
The advantage scales with page complexity. On content-heavy pages the structured orientation is ~10–140x smaller than the full snapshot. On a trivially small page like example.com the two are within ~20% of each other. On a page that small, the structured representation can be the larger of the two, because there is simply nothing to summarize away.
Tool definition overhead
Tool definitions are sent on every API round-trip, whether or not the agent uses them.Per-task token cost
A same-day, same-live-page battery of three scripted agent tasks against Charlotte v0.8.0 (23 tools, 3,825 def tokens) and Playwright MCP v0.0.79 (24 tools, 4,626 def tokens). Full call-by-call sequences:benchmarks/results/tasks/2026-08-09/tasks.md.
Release drift
Charlotte’snavigate orientation cost, tracked across every release against the same live pages, same day (2026-08-09). Full chart and methodology: benchmarks/results/drift/2026-08-09/drift.md.
Charlotte’s orientation cost has stayed within a narrow band across seven releases while the tool surface was cut roughly in half, from v0.3.0’s 36 tools down to v0.8.0’s 23. Playwright’s baseline sits one to two orders of magnitude higher throughout, because its
browser_snapshot scales with page content, not page structure. See the drift report for the live-page-drift and Chromium-version caveats that qualify these numbers.
Live pages drift. Hacker News, Wikipedia, and GitHub content changes day to day, so these numbers include real content drift alongside Charlotte’s own changes. See the linked methodology for the same-day rule and per-version Chromium caveats.