convert_document

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

The description indicates file-based conversion with input/output paths and returns output path or error. However, without annotations, it omits details like overwrite behavior, file size limits, or error handling, limiting full transparency.

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 and well-structured with Args list, Returns line, and supported formats. Every sentence is informative, though the list of formats could be more compact.

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?

The description covers conversion logic and output, but given the large set of sibling tools and the general nature of this tool, it lacks guidance on when to choose this over specialized converters, which is a gap in completeness.

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?

With 0% schema description coverage, the description compensates well by explaining each parameter's purpose and optionality, including auto-detection for from_format and to_format. This adds significant value beyond the bare 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 conversion between document formats using Pandoc and lists supported formats. However, it does not differentiate from the many specific conversion sibling tools (e.g., convert_docx_to_markdown), which reduces clarity on when this general tool is preferred.

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 explains that formats are optional and auto-detected, implying usage for arbitrary conversions. But it lacks explicit guidance on when to use this tool versus dedicated converters, and does not mention prerequisites or 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.