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

Annotations only cover readOnlyHint/openWorldHint, but the description adds substantial behavior the agent could not otherwise know: browser rendering for JS pages, redirect resolution, the 50k truncation limit, the x402 price model, that failed/empty loads are free, the 3-free-calls-per-day tier, and the quote-then-pay round trip. That is exactly the value-add expected on top of annotations.

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?

Four short sentences/paragraphs, each carrying distinct information: what comes back, when to use it, and the payment mechanics. Capability, usage, and cost are front-loaded in that order with no filler.

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?

With no output schema, the description carries the return-value burden itself and does so (visible text, title, redirected URL, size ceiling). Combined with the fully-covered input schema and annotations, an agent has everything needed to call it correctly.

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 description coverage is 100%, so both `url` and `payment` are already documented in the schema, including the omit-to-get-a-quote flow. The description restates the payment quoting behavior but adds no new syntax, format, or constraint beyond what the schema provides, making the baseline 3 the correct call.

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?

States a specific verb and resource ('Read any public web page and get its visible text back') and details the output shape: visible words, nav/boilerplate stripped, title, final URL after redirects, JS rendered, 50k cap. It never names a sibling (page_brief, screenshot_page, pdf_to_text), so the agent must infer the boundary itself rather than being told.

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?

Gives clear positive context ('read an article, a doc, a policy or any page you were given a link to') and even a chaining hint (pair with a summarizer for long pages). It stops short of any exclusion or alternative comparison, so when NOT to use it versus page_brief or search_and_read is left to inference.

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