convert_video_format

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

With no annotations, the description carries the burden for behavioral disclosure. It mentions the codec-copy attempt and a status return, which is helpful, but omits fallback behavior if codec copying fails, whether output file will be overwritten, and specific error conditions. This leaves important operational details unclear.

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 compact and well-structured: a one-sentence behavior statement followed by a clear Args/Returns list. Every sentence serves a purpose, with no filler or redundant schema repetition.

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 is simple (3 parameters, output schema present) and the description covers purpose, parameters, and return type. The fallback behavior for codec-copy failures is implied ('attempting to copy codecs first') but not explicit, and edge cases like unsupported formats are not addressed. Still, it is largely complete for a straightforward conversion 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?

The input schema has 0% description coverage, so the Args section is the sole source of parameter meaning. It provides clear, useful descriptions for all three parameters, including examples for target_format. This adds real value beyond the bare property names.

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's function: 'Converts a video file to the specified target format'. It uses a specific verb and resource, and the phrase 'attempting to copy codecs first' distinguishes it from sibling tools like convert_video_properties or set_video_codec.

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 usage context is implied: use this tool to change the container format. However, it provides no explicit guidance on when not to use it, such as when re-encoding is required, or alternatives like set_video_codec for codec changes. The 'attempting to copy codecs first' hint suggests a remux scenario but does not clearly exclude other tools.

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