Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With readOnlyHint/openWorldHint already declaring the safety profile, the description still adds real behavioral context: real-browser JS rendering, 20,000-character per-page truncation, parallel reads where one failure doesn't stop others, per-call $0.008 x402 pricing, failed-calls-are-free, and the quote-then-pay flow via the payment param. This is far beyond what annotations convey.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loaded with the core action and scoped well, with labeled When/Instead/Params/Returns sections. Slight redundancy: the 20,000-character truncation and per-page failure behavior are stated twice (opening paragraph and Returns), which costs a little tightness.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

No output schema exists, so the description carries the returns burden and does so fully: pages[] in input order with ok, title, final_url, text (or failure reason), plus pages_read/pages_failed and the billing condition. Pricing and the quote flow are also covered, leaving no gap for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3, but the description adds meaning: urls must be 1-5 absolute http(s) URLs read in parallel, and it explains the payment parameter's quoting workflow beyond the schema's terse 'omit to receive a quote'.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

Names a specific verb and resource ('Read several web pages at once'), quantifies the batch (up to 5 URLs), and explicitly contrasts itself with read_page and search_and_read so an agent can distinguish it from siblings without opening schemas.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

Has an explicit 'When to use' line ('You picked 2-5 pages to read, for example from web_search results') plus a 'Use instead' line naming read_page for a single URL and search_and_read for question-only flows. When, when-not, and alternatives are all present.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.