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

With no annotations, the description carries the burden and does disclose the non-obvious traits: it is a paid call ($0.002 USDC via Solana x402) and it only works on public pages. It does not mention rate limits, failure modes for private/blocked pages, or latency, so a small gap remains.

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 tight sentences: capability and return shape first, then the input and cost. Every clause carries information and nothing is padded.

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, but the description enumerates what comes back (title, main text, links), which is the key missing piece. The payment flow is covered by the x402_payment parameter description rather than the description itself, which is acceptable.

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 url, max_chars, and x402_payment are fully documented in the schema. The description repeats only {url} and adds no semantics for max_chars truncation behavior beyond the schema. Baseline 3 applies when the schema does the work.

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), resource (public web page) and output contract (clean Markdown with title, main text, links). An agent can tell this is a page-to-markdown extractor, distinct from summarize (condensation) or the API lookup siblings.

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 description implies usage (fetch a public page) and explains the payment handshake implicitly via 'Costs $0.002 USDC', but never says when to prefer this over summarize or how to handle non-public pages. Usage is implied rather than stated.

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