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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive, so the bar is lower. The description adds meaningful context beyond them: the x402 payment requirement, the exact price, the required X-PAYMENT header, and per-URL charging for batch calls. It does not cover failure modes such as unpaid requests or rate limits.

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, front-loaded with what the tool returns and how it is paid for, with the batching rule last. Pricing and header details are dense but each earns its place; no filler wording.

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 paid, open-world fetch tool with no output schema and no parameter descriptions, the definition covers the core mechanics an agent needs to call it. It falls short on maxChars semantics, error or payment-failure behavior, and any comparison to the many sibling search/crawl tools.

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 0%, so the description has to carry parameter meaning, and it does well for url and urls (max 20, parallel, charged per URL). maxChars is never mentioned in the description or schema, leaving one of three parameters completely unexplained.

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?

The description gives a specific verb and resource ("Fetch a public URL and return clean markdown") plus the payment mechanism and price, so the agent knows exactly what the tool produces. It never distinguishes itself from close siblings such as search_extract or crawl_site, which leaves a small ambiguity gap.

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?

It clearly explains the url-versus-urls choice and that batching is parallel and billed per URL, which is real usage guidance. It gives no guidance on when to prefer this tool over crawl_site, search_extract, or web_search, and no prerequisites beyond the payment header.

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