convert_file

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

With no annotations, the description carries the full behavioral burden. It usefully discloses the side effect ('save the output to disk') and the default write location, but says nothing about overwriting existing files, whether the source is modified, permission requirements, or what happens on an unsupported source/target combination.

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 purpose sentence is front-loaded and the Args block is scannable per-parameter. Slightly verbose with blank lines between entries, but no sentence is wasted.

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?

An output schema exists, so return values need not be documented, and the description covers purpose, all parameters, and the write destination. Remaining gaps are error/edge-case behavior (unsupported conversions, overwrite handling) rather than anything blocking a correct invocation.

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 0%, so the description must compensate, and it largely does: it explains all three parameters and enumerates the valid output_format values per media type, information absent from the schema (no enum constraints defined). It stops short of specifying format syntax (extension vs. mime), case sensitivity, or whether the format can be inferred from the file.

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?

States a specific verb (convert), resource (local image or video), and outcome (save the output to disk) with an explicit scope qualifier ('local'). The siblings (analyse_file, hide_file, reveal_file) are unrelated operations, so no disambiguation text is needed for the agent to pick this tool correctly.

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?

Usage is implied by 'local image or video' plus the format lists, which tell the agent what inputs are in scope. However, there is no explicit when-to-use statement, no exclusion for cross-type conversions (e.g. image → mp4), and no mention of failure modes or prerequisites.

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