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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is covered. The description contributes the noise-stripping/token-efficiency framing and the endpoint path, but says nothing about truncation, size limits, or how scripts/styles/nav elements are treated. With annotations carrying the safety burden, this is adequate but not rich.

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 compact clauses with the core action front-loaded and the endpoint tucked at the end. The 'LLM HTML-to-Markdown Cleaner API' branding prefix is slightly redundant with the tool name but costs little.

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 simple single-parameter transform with rich annotations and no output schema, the description covers what the tool does and why. The only meaningful gap is the absence of any note on input size or what constitutes 'clean' output.

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?

There is a single parameter with 100% schema description coverage, so the schema already defines 'html'. The description adds no format or size guidance for the input beyond what the schema states, which is the expected baseline for a one-parameter tool.

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 names a specific verb and resource (convert HTML into Markdown) and adds the intended outcome (clean, token-efficient output for RAG). It does not explicitly distinguish itself from any sibling, but no sibling is in the same domain, so the risk of confusion is low.

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 only implied: 'noisy web pages or raw HTML' suggests the input type, and 'for RAG' hints at the workflow context. There is no explicit when-to-use/when-not-to-use guidance, no note about whether to use it before or after a chunking tool like tinplate_rag_chunker, and no stated input-size limits.

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