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

With no annotations, the description carries the burden and does well: it discloses that scripts, styles and navigation are stripped, that output is truncated to maxChars, and that each call costs 0.005 USDC via x402. It does not describe failure modes (non-200 responses, timeouts, non-HTML pages) or rate limits, which keeps it from a 5.

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?

Two sentences, zero waste: the capability and return payload are front-loaded, and pricing follows. Every clause carries information an agent needs.

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?

There is no output schema, so the description properly enumerates the returned fields and explains truncation and the paid-call model. Only error and edge-case behavior is missing, which is a modest gap for a fetch tool.

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 67%; the two documented params cover url and the payment flow. The description adds meaning for the undocumented maxChars by explaining it truncates the extracted text, while bounds and default come from the schema. Slightly short of full because it doesn't restate that omitting paymentProof triggers the 402 challenge (that lives only in the schema).

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?

Specific verb plus resource: 'Downloads a public URL and returns...' followed by an enumeration of exactly what is returned (title, meta, canonical, OG tags, headings, link count, main text). That level of specificity separates it from URL-structure tools like url_parse without naming a sibling explicitly.

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: fetch the readable content of a public page. There is no explicit statement of when to prefer this over url_parse or ai_extract, and no stated exclusions (e.g. non-HTML content, paywalled or private URLs).

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