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

Beyond the minimal annotations (readOnlyHint=false, destructiveHint=false), the description discloses substantial behavior: which formats are input-only (heic/svg/psd), that alac is delivered as .m4a, that legacy video formats are re-encoded to mp4, audio-extraction paths, and subtitle conversions. This adds real behavioral context the annotations cannot convey.

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 content is dense and front-loaded with the core purpose, but the entire payload is one enormous run-on sentence crammed with slashes and parentheticals. Every item arguably earns its place, yet the lack of structural breaks (bullets or clauses) makes the format matrix harder to parse than it should be.

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 3-parameter tool with no output schema and no enums, the description covers the supported domain remarkably well: all conversion families, input-only formats, output container caveats, and sibling routing. The main gap is that it never states what the response looks like (the converted file payload), which matters more given there is no output 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 coverage is 100% and each parameter has a description, so baseline is 3. The description adds value beyond the schema by effectively enumerating valid values for `to`/`from` (the full format lists) and clarifying pairings (e.g., image→image, audio→audio), which the schema does not constrain with enums. It supplements but does not fully duplicate 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 states a specific verb and resource ('Convert a file between formats') and enumerates the exact conversion matrix. It explicitly distinguishes itself from siblings by naming convert_document, convert_archive, and convert_data as the homes for Office, archive, and data conversions, so an agent can tell this tool apart without opening schemas.

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 explicitly routes non-matching workloads to named alternatives ('Office/document conversions ... live in convert_document; archives in convert_archive; data formats in convert_data') and flags the 'Business gate on some edges' for video conversions. This is explicit when-to-use vs when-not-to-use guidance.

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