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

With no annotations, the description carries the full burden and does meaningful work: no API key, no URL fetching, no script execution, and notably that inputs are not stored (a privacy guarantee an agent cannot infer from structured fields). It omits failure behavior and the input size ceiling, but the core behavioral profile is disclosed.

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 conversion sentence is front-loaded and efficient, but the trailing 'Optional interview is independent of use.' is cryptic, reads as unrelated boilerplate, and does not earn its place in a tool description. Removing it would sharpen the definition.

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 stateless two-parameter converter with no output schema and no annotations, the description covers the main behavior and constraints, so the omission of return-value detail is acceptable. However, leaving base_url semantics and the input size limit undocumented leaves a real gap an agent may hit on relative links or long documents.

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 0%, so the description must compensate and largely does not. The 'html' parameter is implied by 'Convert provided HTML', but 'base_url' is never mentioned in the description despite being relevant to resolving relative links, and the html maxLength of 10000 is left to the schema.

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 and resource ('HTML to Markdown conversion', 'Convert provided HTML') and enumerates the constructs handled (headings, lists, emphasis, links, code). No sibling tool overlaps this resource, so an agent can select it unambiguously without opening the schema.

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?

Gives a clear context of use ('for reading or RAG') and explicit exclusions ('No URL fetching or script execution'), which tells the agent this is not a scraper. It does not name an alternative sibling, but none of the listed siblings performs a comparable conversion, so the routing risk is low.

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