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

Annotations only cover readOnly and openWorld; the description adds genuinely new behavior: a $0.003 USDC charge on Base, the x402 payment flow, and the fact that unpaid calls return PaymentRequired rather than failing silently. This is high-value context that structured fields do not carry. Minor gap: no statement on truncation semantics when maxChars is hit or on non-HTML URLs.

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?

Three tight sentences: capability and return shape first, use case second, cost/payment mechanics last. No redundancy with the title and nothing that fails to earn its place.

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?

No output schema exists, so the description carries the return contract — and it does, naming Markdown content, title, word count and final URL. Combined with the payment disclosure, an agent has everything needed to call this correctly and handle the 402 case.

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 both parameters are already documented with ranges and defaults. The description adds only an indirect hint about redirect handling via "final URL"; it adds nothing about url format or maxChars behavior beyond what the schema provides, so baseline 3 applies.

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 (Fetch) and resource (public web page) and precisely names the return artifact: main-content-only Markdown plus title, word count and final URL. That clearly separates it from siblings like url_metadata, url_links and url_check, which an agent can rule out without opening schemas.

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?

"Ideal for feeding pages to an LLM" gives a clear use context, and the main-content-only framing signals when this beats a raw fetch. However, it never explicitly names alternatives (url_metadata, url_links) or states when-not to use it, so routing between siblings 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.