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

No annotations are provided, so the description carries the full disclosure burden. It usefully scopes supported syntax (headings, bold, italic, code, links, lists, quotes), which tells the agent what input is handled, but it omits whether output is a fragment or full document, how unsupported syntax or malformed input is treated, and whether the operation is pure/side-effect-free.

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?

A single front-loaded sentence with the core verb-resource pair first and the supported-construct list as a compact parenthetical. Nothing is wasted, though the parenthetical could have been spent on more decision-relevant detail.

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 converter, the description covers purpose and supported syntax but leaves return-shape ambiguity (fragment vs. full HTML document) and error behavior unexplained. Adequate but not fully self-sufficient.

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% for the single 'markdown' parameter, so the description must compensate. It implicitly confirms the input is Markdown source text, but adds no detail about expected format, escaping, or size limits beyond the schema's type declaration; the parameter name is self-evident enough that this gap is minor.

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 ('Convert Markdown to HTML') and enumerates the supported constructs, so the agent knows exactly what transformation happens. It does not name the inverse sibling html_to_text, but the direction of conversion is unambiguous from the name alone.

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?

There is no when-to-use or when-not-to-use guidance, and no reference to alternatives such as html_to_text for the reverse direction. Usage is only implied by the tool name.

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