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

The description adds meaningful context beyond the annotations: it discloses a $0.01 USDC payment requirement, a payTo address, and the 'public URL' constraint. The readOnlyHint and openWorldHint annotations are not contradicted. It does not explain payment mechanics or error behavior, but the added context is valuable.

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?

The description is short, but the payment phrase is front-loaded awkwardly before the actual verb, and the payTo address appears as a detached second sentence. It is not verbose, but the structure could better prioritize the core action.

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 tool with annotations and no output schema, the description covers purpose, return type, and payment context. However, the payment requirement is ambiguous ('Paid $0.01 USDC exact on Base' could mean already paid or required), and there is no mention of error handling, redirects, or content limitations.

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 the url parameter is already described as an 'http(s) URL to inspect' with no payment headers sent. The tool description adds only the word 'public' and the output format, which is marginal beyond the schema. Baseline 3 is appropriate.

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 clearly states a specific action: 'fetch a public http(s) URL and return simple HTML-to-text markdown.' This distinguishes it from sibling tools like headers, json, and domain. The payment prefix is unusual but does not obscure the core purpose.

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: use this tool when you need HTML-to-text markdown from a public URL. However, there is no explicit when-not-to-use guidance or mention of alternatives among the sibling tools. The payment requirement is a usage condition but is not framed as a selection criterion.

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