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

Goes well past the annotations (which only say readOnly/openWorld/idempotent) by disclosing pricing ($0.002/call, x402 USDC on Base), the free-trial rule (3 per IP per UTC day), a hard 60,000-character cap, robots.txt compliance, and ~1-3 s latency. It also explains truncation behavior and a truncated flag, which is exactly the operational context an agent needs before spending a call.

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 and largely front-loaded, but the lead position is given to pricing rather than the resource, and the trial mechanic is stated twice (in prose and again via the schema's trial parameter). The bracket tag "[Fetch and read the web]" and the title's pricing repetition are mild padding, yet no sentence is genuinely wasted.

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?

For a 4-parameter read tool with an output schema, this covers everything material: scope, cost model, size/latency limits, robots.txt behavior, and the two shaping options. Nothing an agent needs to decide whether and how to call it 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 description coverage is 100%, so the baseline is 3, and the description largely restates what the schema already documents (include_links=false for text only, max_tokens 100-100000 cut at block boundaries). It adds no syntax or edge-case meaning beyond the structured fields, so it neither compensates nor detracts.

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 concrete verb and resource: "Fetch one public web page and return its main content as clean Markdown," and enumerates exactly what is stripped (nav, cookie banners, footers, share bars) and preserved (headings, nested lists, links, alt text, pipe tables, fenced code). An agent knows precisely what it gets, but nothing distinguishes it from the very similar sibling page_markdown_batch or from readability/text_extract.

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?

Usage is implied ("for agents and RAG", "read any public web page") rather than stated as a when-to-use rule. The only explicit routing is the payment escape hatch ("add trial: true or use try_free"), which is about billing, not tool selection; there is no guidance on when to pick page_markdown_batch, readability, or page_meta instead, and no exclusion such as JS-rendered pages.

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