convert_html_to_markdown

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

The description only states the conversion operation, but adds no behavioral context beyond what the annotations provide. It does not disclose output format, edge cases, or any side effects, leaving the agent uninformed about how the tool behaves.

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 extremely concise with a single sentence. While it is front-loaded and waste-free, it may be too brief to fully inform the agent, but it earns its place by stating the core function.

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 tool with no output schema and minimal annotations, the description lacks important contextual details such as the return format, examples, or limitations. It is insufficient for an agent to fully understand the tool's operation.

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 has 100% coverage for the single parameter, so the baseline is 3. The description does not add any additional meaning or constraints beyond the schema's own documentation of the 'html' parameter.

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 conversion from HTML to Markdown, using a specific verb and resource. However, it does not differentiate itself from sibling tools like 'convert_markdown_to_html' or other converters, limiting its usefulness in distinguishing between similar tools.

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 guidance on when to use this tool versus alternatives, no mention of when not to use it, and no explicit or implicit usage context. The description provides zero decision support for an agent.

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