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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description earns credit for adding a behavioural fact the annotations do not carry: the operation costs 1 credit, plus an expectation about output quality ('clean, semantic HTML'). Input limits and error behaviour are left to the schema/output schema.

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 substance is a single efficient sentence, but it is prefixed by a redundant 'Markdown to HTML: Markdown to HTML is a markdown converter API' restatement of the name and title, and the closing credit note is parenthetical rather than integrated. Nothing is front-loaded beyond the repeated name.

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 pure-conversion tool with annotations and an output schema, the description covers purpose, cost, and output character adequately. The remaining gaps (supported Markdown dialect, how the cost is charged on failure, input limits) are modest but real for a paid, open-world call.

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, including the 100,000-character maximum and an example payload, so the schema carries the load. The description adds no parsing semantics such as supported Markdown flavour (CommonMark/GFM), escaping behaviour, or how raw HTML inside the input is treated.

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 clear verb+resource pairing ('parses markdown syntax and converts it to clean, semantic HTML') and states the intended downstream use (web rendering, content management). It does not differentiate itself from near-neighbours such as MarkdowntoPDF, MarkdowntoImage, or URLtoMarkdown, so an agent still has to infer which converter it wants.

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 explicit when-to-use or when-not-to-use guidance, and no alternative is named despite the catalog containing several closely related converters (MarkdowntoPDF, MarkdowntoImage, URLtoMarkdown, HTMLtoText). The only selection hint is implicit in the phrase 'suitable for web rendering', which is thin.

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