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

Goes well beyond annotations: it discloses that raw HTML is escaped (a security/safety trait the agent must know), explains the pricing model including free tier and that failed calls are free, and explicitly reconciles the readOnlyHint=false annotation by noting calls are charged. This is meaningful context the structured fields do not carry.

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?

Front-loads the conversion and supported features, then adds behavior and pricing. Mostly efficient, though the inline example is crammed together and the pricing sentence is a run-on that slightly muddies the structure.

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 single-parameter, no-output-schema tool, the description covers purpose, supported syntax, safety behavior, and billing. Nothing critical for correct invocation is missing.

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 coverage, so the schema already documents it. The description's example illustrates usage but adds no new syntactic meaning beyond 'The Markdown'.

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+resource ('Convert Markdown ... to HTML') and enumerates the supported Markdown constructs, making the transformation unambiguous. It is clearly distinguishable from the reverse-direction sibling html_to_text.

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?

Provides an explicit use case ('publish agent-written Markdown on a web page') and a concrete example input. It does not name alternatives or state when-not-to-use, but the context is clear enough to route correctly.

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