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

With no annotations, the description carries the full burden and does well: it discloses automatic provider failover, the exact price ($0.008 USDC on Base), that charging happens only on success, and the failure contract for unpaid calls including the retry key. It omits timeout/rate-limit behaviour and any note on JS-rendered or blocked pages, 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?

Three short sentences, front-loaded with what the tool does, then cost, then the retry contract. Every sentence carries operational information and none is filler.

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 one-parameter, no-output-schema tool the description covers the essentials an agent needs before calling: the output form (clean markdown), the reliability model (failover), and the payment protocol end to end. What is missing is edge-case behaviour (timeouts, empty/JS-only pages, truncation of very large pages).

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% and there is only one parameter, whose schema description already says 'Public http(s) page to convert to markdown.' The description adds no extra constraint on the url (e.g. auth-gated pages, redirects, size limits), so it sits at the baseline rather than compensating.

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 states a specific verb and resource ('Page to clean markdown') plus the routing behaviour ('healthy provider with automatic failover'), which is more than a restated title. It never mentions the sibling tools scrape_lite or quote, so an agent cannot tell from the text why it should pick this paid variant over the lite one.

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 guidance is limited to the payment handshake: unpaid calls return x402 requirements and should be retried with _meta["x402/payment"]. That is genuinely actionable for the calling flow, but there is no guidance on when to prefer this over scrape_lite or quote, which is the main selection decision an agent faces.

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