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

Goes well beyond the annotations: it discloses redirect following, robots.txt compliance, content-stripping heuristics, the metadata fields returned, and a prompt-injection warning that page text is third-party data and never instructions. It also surfaces cost ($0.002 USDC on Base) and the exact two-step x402 payment flow, none of which the readOnlyHint/openWorldHint 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 capability and the return shape, then the safety caveat, then pricing and the payment flow — a sensible ordering. It loses a point for redundancy: the price is stated twice ('$0.002 USDC on Base via x402. Price: $0.002.') and the parenthetical keyword list (web scraper / html to markdown / reader) adds bulk without adding selection signal.

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 and does so by naming title, description, author, date, canonical URL and word count. The paid-call flow is fully explained, which is essential for a 402-gated tool. The remaining gap is max_chars behavior on truncation, which an agent needs to call the tool 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 coverage is 33% and uneven: x402_payment is fully documented in the schema, url is self-evident, but max_chars (500–100000) is undocumented in both schema and description — the description never says whether it truncates, how truncation is signalled, or that word count reflects the truncated text. The payment mechanics in the description partly compensate for the payment params but not for the length-control param.

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 a web page, return clean Markdown) and supports it with concrete behaviors: follows redirects, strips nav/ads/scripts, preserves headings/lists/code/tables. It also enumerates returned metadata, which lets an agent distinguish it from a pure metadata tool. However, it never names url_metadata_link_preview, the closest sibling, so the boundary between 'page content' and 'link preview' is left to inference.

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?

The payment handshake is spelled out precisely (first call returns PaymentRequired with no charge, retry with payment in _meta["x402/payment"]), which is genuinely actionable usage guidance. But there is no statement of when to choose this over url_metadata_link_preview or image_to_text_ocr, and no exclusions (e.g. paywalled or JS-rendered pages). Usage is implied by capability rather than stated as selection criteria.

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