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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive, so the safety profile is covered. The description adds a key behavioral detail: 'Scripts/styles are dropped on html→md', which is not in the annotations and helps the agent anticipate output loss. No contradictions.

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 sentences with no fluff. The core action is stated first, then flavor and behavior details follow. Every clause earns its place; the 'Price: free' is extra but harmless and short.

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 simple conversion tool, the description covers purpose, direction, Markdown flavor, a critical behavioral note (dropping scripts/styles), and even pricing. There is no output schema, so no return format is needed. An agent has enough to call it correctly.

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 coverage is 0%, so the description must compensate. It implies the 'to' parameter selects direction ('Convert Markdown... or HTML back to Markdown') and that 'input' holds the content, but it doesn't explicitly map these to parameter names. The enum values make 'to' self-explanatory, so the description adds marginal value beyond the schema.

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 clearly states the tool converts between Markdown and HTML, specifies GitHub-flavoured Markdown features (tables, task lists, fenced code), and distinguishes it from any conversion siblings by naming both directions. It is specific and unambiguous.

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 makes the intended use explicit: convert Markdown to HTML or HTML back to Markdown. It mentions the direction and the libraries used, which implies when to use it. There are no competing conversion tools among siblings, so no exclusions are needed, but it stops short of stating 'use this when you need X'.

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