convert_document

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only promises high-fidelity layout preservation and says nothing about engine auto-selection, whether the source file is modified, default output behavior when output_path is omitted, OCR behavior, or failure conditions. This leaves key behavioral traits undisclosed.

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 a single front-loaded sentence with a clear verb, compact format list, and no filler. It is efficiently structured and immediately scannable, even though it sacrifices depth.

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 nested options, no annotations, and no output schema, this description is too thin. It omits default output behavior, engine selection semantics, and boundary conditions, and its format list overlaps with several sibling tools, leaving an agent without enough context to invoke it confidently beyond 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 75%, so the schema already documents most parameters. The description adds context about supported input formats and preservation intent, but it does not explain interaction between options, output path defaults, or format compatibility 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 the operation as document conversion, lists supported formats (DOCX/DOC/PDF/RTF/ODT/TXT/HTML/MD), and highlights high-fidelity layout preservation. It is specific about the resource and action, though it does not explicitly differentiate from overlapping siblings like convert_pdf or convert_markup.

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 format list implies usage for converting documents among these types, but there is no explicit guidance about when to choose this tool over convert_pdf, convert_markup, convert_ebook, or other siblings. No exclusions or alternative routing are provided, so usage is mostly inferred.

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