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

Beyond the annotations (readOnlyHint=true, destructiveHint=false), the description adds significant behavioral detail: it strips scripts/nav/ads, preserves headings/links/lists/emphasis, requires no browser/LLM/API key, and mentions cost. This fully sets expectations about what happens during conversion and what the output will look like.

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 and front-loaded with the core function, followed by supporting details. The pricing/method detail ('$0.01/call, x402') is arguably extra but still useful context. A small redundancy exists ('cheaply' vs. pricing), so it is not perfectly concise.

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?

Given no output schema, the description explains the return format conceptually (clean Markdown) but does not explicitly state how multiple URLs' results are returned (e.g., an array of markdown strings). It also omits failure/error behavior. However, the tool is simple, and the schema's 'One row per URL' partially covers this, so it is still fairly complete.

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?

The input schema already provides 100% coverage with clear descriptions for all three parameters. The tool description adds overall context (what 'convert' means) but does not add new parameter-specific semantics. Since the schema carries the load, the 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 uses a specific verb+resource: 'Fetch any URL and convert it into clean, LLM-ready Markdown', and enumerates the preserved/stripped elements. This clearly distinguishes it from sibling tools like sitemap-to-knowledge or structured-extract, which have different outputs and use cases.

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 states it is 'Built for RAG pipelines and AI agents that need one page turned into readable text, cheaply', giving a clear target use case. It also implicitly contrasts with alternatives by noting 'No browser, no LLM calls, no API key', but does not explicitly name alternative tools or say when not to use it, so it's not a full 5.

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