convert_file

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

With no annotations provided, the description must disclose behavioral traits. It states the conversion direction but does not mention whether it is read-only, how it handles edge cases (e.g., unsupported Markdown elements), or what the return format is. This is minimal for a tool with zero annotation coverage.

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 one sentence, front-loaded with the verb, and zero wasted words. It is immediately clear and concise.

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 moderate complexity (nested options), no annotations, and no output schema, the description is minimal but covers the core purpose. However, it lacks context about return values, error behavior, and option implications, though those are partially discoverable from the schema.

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 description coverage is 50% (path is described, options is not). The description adds no parameter semantics or context about the options object. While the schema's individual property descriptions exist, the description fails to compensate for the missing top-level parameter explanation.

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 a specific verb ('Convert') with a specific resource ('local markdown file') and output ('plain text'). It distinguishes from sibling tools by explicitly targeting local files, unlike convert_text or convert_url.

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 implies use for local markdown file conversion but does not explicitly mention when not to use it or name alternative tools. Sibling tools are listed in context, but the description itself provides no exclusions or alternatives, leaving the agent to infer based on the tool name.

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