convert_file

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

With no annotations, the description carries the behavioral disclosure burden. It discloses the output location ('next to it'), the single-file constraint, no batch mode, and the limited-but-large set of proven conversions. It does not mention error behavior for unsupported formats, but it preempts that with the pointer to list_conversions.

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?

Three sentences with no fluff: purpose and output location first, then capability scope, then a usage instruction and constraint. Every sentence earns its place and the key operational detail is front-loaded.

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 annotations, the description covers the essential operational constraints, points to the sibling tool for verification, and pairs well with the fully documented schema. It could mention what happens on failure or unsupported pairs, but the list_conversions pointer mitigates that gap.

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 the schema already documents all three parameters including the 'bare extension' format and overwrite behavior. The description adds context about supported format families and one-file-per-call, but it does not add significant parameter-level meaning 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?

States a specific verb and resource: convert one local file to another format and write the result next to it. It also gives concrete scope (3649 conversions across 162 input formats) and clearly separates itself from the sibling list_conversions by focusing on performing a conversion rather than enumerating supported pairs.

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?

Explicitly tells the agent to call list_conversions first when unsure whether a pair is supported, and warns that there is no batch mode and only one file per call. This gives clear when-to-use and 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.