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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, covering the safety profile. The description adds valuable behavioral context beyond annotations: it strips scripts/nav/ads, requires no browser or LLM calls, and costs $0.01/call. These details are not redundant with annotations and help the agent understand side effects and constraints.

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 concise and well-structured. The first sentence captures the core function, followed by practical details (cost, dependencies, use case). No filler or redundancy; the pricing and target audience are stated succinctly.

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 tool with 3 parameters (1 required), no output schema, and robust annotations, the description is largely complete. It explains the output concept ('LLM-ready Markdown') and key behavioral facts (stripping, cost, no dependencies). However, it does not explicitly describe how the markdown is returned (e.g., as a string or structured object), nor how errors or multiple URLs are handled, leaving minor gaps.

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 description coverage is 100%, so the baseline is 3. The description does not add extra meaning about the parameters themselves; it only mentions 'headings, links, lists and emphasis preserved' which loosely relates to includeLinks but doesn't explain the parameter semantics beyond what the schema already provides. Since the schema fully documents each parameter, no additional credit is warranted.

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 the tool's function with a specific verb and resource: 'Fetch any URL and convert it into clean, LLM-ready Markdown'. It distinguishes from siblings by detailing what is preserved (headings, links, lists, emphasis) and what is stripped (scripts/nav/ads), making it unique among the listed tools.

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 provides clear context for when to use the tool: 'Built for RAG pipelines and AI agents that need one page turned into readable text, cheaply.' It does not explicitly state exclusions or alternatives, but the use case is well-defined and differentiates from sibling tools. The mention of no browser/LLM/API key also helps the agent decide if it fits.

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