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

No annotations exist, so the description carries the full burden. 'Pure CPU, instant' usefully signals no external calls, no auth, and deterministic local execution, which is real added context. It says nothing, however, about whether unsupported Markdown is passed through, whether the emitted HTML is sanitized, or whether the result is a fragment or a full document.

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 short sentences with zero filler, and the capability statement is front-loaded before the performance note. Every clause earns its place by naming a supported construct.

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 one-parameter, annotation-free, output-schema-free pure function, the description covers input, output, supported syntax, and execution characteristics. The only real gap is post-conversion behavior such as sanitization or wrapping, which matters for HTML output but is secondary here.

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 required parameter with 100% schema description coverage, so the schema already labels the input as 'Markdown text'. The description adds no formatting expectations, size limits, or syntax caveats beyond that baseline.

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 gives a specific verb and resource ('Convert Markdown to clean HTML') and enumerates the constructs handled (headings, tables, code fences, links). That distinguishes it from near siblings like html_minify or ascii_table, though it never names an alternative explicitly.

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 by the tool's obvious input/output pairing; there is no statement of when to pick this over html_minify, html_table, or ascii_table, and no preconditions or exclusions are given. An agent can infer the intent but gets no routing guidance.

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