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

With no annotations provided, the description must shoulder the behavioral disclosure burden, but it only states that conversion occurs. It does not mention the return format (HTML/Markdown string), default direction, escaping/edge-case behavior, or any limitations. No contradiction exists, but the transparency is minimal.

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 or repetition. It conveys the essential purpose in the fewest words possible.

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 two-parameter converter with a complete schema, the description is adequate: it names the conversion formats and relies on the schema for direction and defaults. Lacking an output schema, it would benefit from explicitly stating the return value, but the behavior is reasonably inferable.

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?

The input schema documents both parameters ('input' and 'direction') with 100% coverage, so the baseline is 3. The description adds no further parameter-specific details; however, it reinforces the conversion context by mentioning both formats.

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 uses a specific verb ('Convert') and names the exact formats ('Markdown and HTML'), clearly identifying the tool's core function. It implies bidirectional conversion but does not explicitly differentiate itself from sibling tools like markdown-editor or html-sanitizer.

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?

No guidance is provided about when to choose this tool over alternatives such as markdown-editor, html-sanitizer, or format-converter. The intended use is only implied by the verb 'Convert,' with no exclusions or prerequisites.

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