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

Annotations already cover read-only, idempotency and open-world access, but the description goes substantially beyond them: it discloses that scripts/styles are stripped, output is capped, the converter is Turndown, and that a paid x402/Solana charge of $0.005 applies per successful call. Cost and output-truncation behavior are exactly the traits structured fields do not convey.

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?

Four compact sentences, front-loaded with what the tool does, followed by output behavior, use case, and pricing/alternate endpoint. No sentence is redundant and nothing restates the title.

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 single-parameter fetch-and-convert tool with no output schema, the description covers purpose, output transformation, cost, and an alternate HTTPS endpoint. Remaining gaps are error behavior for non-HTML pages, unreachable URLs, and how payment failure is surfaced.

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 0% for the single 'url' string, so the schema provides no semantics at all. The description partially compensates by implying the URL must point to a public HTML page (not JSON, PDF, or authenticated content), but adds no format, length, or redirect-handling detail.

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+resource: fetches a public HTML page and converts main/article content to Markdown via Turndown. That distinguishes it somewhat from html_to_markdown (which implies an HTML-string input), but the description never names or contrasts that near-identical sibling, leaving an agent to infer the difference.

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?

'Good for RAG/agent ingestion' gives clear intended context, and 'public HTML page' implicitly excludes authenticated or non-HTML targets. However, no alternative tool (html_to_markdown, web_to_text, readability_extract) is named and no explicit when-not guidance is given.

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