Markdown Converter

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

With no annotations provided, the description carries the full burden and successfully discloses key behavioral traits: it 'strips tags' and specifically 'preserves headings, lists, code blocks, links, and tables.' It also notes the output is 'clean Markdown.' Minor gap: no mention of error handling for malformed input or Markdown flavor specifics.

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?

Three sentences with zero waste: first establishes capability, second details HTML→Markdown use case with preservation specifics, third covers Markdown→HTML. Front-loaded with the core function and maintains tight focus throughout.

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 utility with 100% schema coverage and no nested complexity, the description is complete. It explains the conversion behavior, directional use cases, and preservation characteristics. No output schema exists, but the return value is implied by the 'to' parameter context.

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 100% with clear descriptions for all three parameters (content, from, to) and explicit enums. The description adds directional context (HTML→Markdown vs Markdown→HTML) that contextualizes the enum values, but does not need to explain parameter mechanics since the schema is fully self-documenting.

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 opens with specific verbs ('Convert') and clear resources ('HTML', 'Markdown'), immediately establishing the bidirectional capability. It effectively distinguishes from siblings like extract_from_text or fetch_url_metadata by focusing purely on format conversion rather than extraction or analysis.

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 explicit directional guidance: 'Use HTML→Markdown when you've fetched a web page and need readable text for an LLM' and 'Use Markdown→HTML when rendering content in a web context.' This clearly defines when to use each conversion direction based on the downstream use case.

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