convert_markdown

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

No annotations are present, so the description should fully disclose behavior. It only states the basic conversion function without any detail about error handling, behavior when both parameters are provided, or size limits. This is a significant gap for a tool with no annotations.

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 concise (two short paragraphs) and front-loaded with the main purpose. The parameter list is well-structured. It could be slightly more concise but effectively conveys necessary information.

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?

Given the existence of an output schema (not shown but indicated), the description adequately covers the input semantics. It explains the two-parameter setup and their uses. However, it does not address edge cases like both parameters provided or empty input, which leaves minor gaps.

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%, but the description fully compensates by explaining each parameter in detail: 'html — HTML content to convert to markdown' and 'markdown — Markdown content to convert to HTML.' It also clarifies the requirement to provide at least one parameter, adding meaning 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 'Convert between HTML and Markdown formats' with specific verbs and resources. It distinguishes itself from sibling conversion tools (e.g., convert_case, convert_color) by focusing on this bidirectional conversion.

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 clear usage context: 'transform web content into clean markdown or convert markdown to HTML for display.' It mentions the condition 'Provide at least one parameter.' However, it does not explicitly exclude alternative tools or specify when not to use it.

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