Convert a document to another format

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

With no annotations, the description carries the transparency burden. It discloses the engine (LibreOffice-WASM) and return format (base64), but lacks details on size limits, timeouts, supported input formats, or error conditions. It provides some behavioral context but not comprehensive.

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?

Two sentences, no fluff. Key information is front-loaded (verb and resource) and every word adds value. Highly efficient.

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 no output schema, the description explains the return value (converted bytes as base64). It covers the conversion mechanism and fidelity aspect. Minor gaps: no mention of input format constraints or error scenarios, but overall sufficient for a relatively simple tool.

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 100%, so baseline is 3. The description adds value by providing example target formats (pdf, html, png) that go beyond the schema's single example, and clarifies that the input is base64-encoded. This enriches parameter understanding.

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 tool converts a document to another format, with examples like pdf, html, png, and mentions using LibreOffice-WASM. It distinguishes from sibling tools (apply_edits, parse_document, preview_document, render_document) by specifying conversion as the core action.

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 usage for fidelity-critical conversions without native LibreOffice, but it does not explicitly compare with siblings or provide when-to-use vs when-not-to-use guidance. Context is somewhat implied but not directly actionable.

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