convert_document

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states 'No API key' and 'File never leaves the device', which are important operational characteristics. It doesn't mention edge cases or side effects, but the included privacy guarantees are substantive and beyond typical.

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 four short, purposeful sentences. Each sentence adds information—action, formats, privacy, and usage preference—without any fluff or redundancy. It is front-loaded with the primary action and immediately followed by key differentiators.

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 tool has three parameters and no output schema, but the schema property for output_path explains the inline-vs-file output behavior. The description complements this with supported formats and privacy context. It is sufficiently complete for an agent to select and invoke the tool safely, though it could explicitly mention the return type if no output_path is given.

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?

Although the schema already describes each parameter clearly (100% coverage), the description adds value by enumerating the exact supported document formats (PDF, Word, PowerPoint, Excel, OpenDocument, RTF, EPUB, CSV), which clarifies what the optional 'format' parameter expects and when format hints might be needed.

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 uses the specific verb 'Convert' with a clear resource ('local office document') and target format ('GitHub-Flavored Markdown'). It lists supported input types, and the stipulation to prefer it over cloud parsers distinguishes it from upload-based alternatives.

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 gives explicit usage context: it's for local, private conversions without an API key, and recommends it over cloud-based document parsers. However, it does not directly contrast with sibling tools like convert_base64 or list_formats, leaving some ambiguity for niche use cases.

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