markdown_to_html

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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by specifying GFM support including tables, code blocks, and task lists, but does not disclose details like HTML escaping behavior, which are only present in the schema parameter description.

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 a single front-loaded sentence with no filler. The core action comes first, and the supported feature set is stated compactly in the second sentence.

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 low-complexity conversion tool, the description plus schema and annotations are nearly sufficient. The only minor gap is that it does not explicitly state the return type as an HTML string, though this is strongly implied by the phrase 'Convert Markdown text to HTML.'

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 schema already documents both markdown and allow_html. The description adds no additional parameter-level meaning, but none is needed given the complete schema coverage.

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 states a specific verb and resource: 'Convert Markdown text to HTML.' The output direction is unambiguous, and naming HTML clearly distinguishes it from sibling converters like html_to_markdown and markdown_to_pdf.

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 clearly implies when to use the tool: whenever Markdown must be converted to HTML. It does not explicitly name alternatives or provide exclusion criteria, but the context is clear enough for an agent to select it among the converter siblings.

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