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

Beyond the annotations (readOnly, idempotent, openWorld), it discloses pricing per URL, that over-limit and fully-failed calls are not charged, per-URL error statuses, timeout bounds (typically 1-5 s, 20 s cap), and a prompt-injection caution about treating page text as untrusted. That is substantial context an agent could not get from structured fields.

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?

Dense but nearly every clause carries information (pricing, limits, behavior, safety). The opening 'Price: USD 0.002 per URL' is front-loaded and useful, though the run-on enumeration of ignored options and edge cases makes it slightly crowded.

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?

An output schema exists, so return-shape explanation is not required, and the description still covers cost model, error handling, timeouts, JavaScript limitation, and ignored parameters. Nothing an agent needs to invoke it correctly is missing.

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; the description adds value by naming the effective inputs ('urls' and optional 'text') and warning that highlights, summary and other common-API options are accepted and ignored. It does not explain the maxCharacters sub-option, so it stops short of a 5.

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?

The description uses a specific verb and resource ('Get the contents of 1-10 URLs: web page to text for a list of URLs') and pins down the output form (Markdown, 50,000 chars, results plus per-URL statuses). It does not distinguish itself from the listed sibling html_to_text, so it falls short of a 5.

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?

States clear selection criteria — 'For one page with JavaScript use render_page' and 'Static fetch only, no JavaScript' — plus a hard limit ('More than 10 URLs is a 422 (not charged)'). It never mentions the html_to_text sibling, so guidance is clear but not exhaustive.

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