Convert video format

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states that the tool re-encodes and mentions a quality setting, without disclosing potential side effects like overwriting existing files, processing time, whether audio streams are preserved, or the lossy nature of re-encoding. This is a significant transparency gap for a conversion tool.

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 a single sentence that is front-loaded with the core action ('Re-encode a video') and includes essential details (container formats and quality setting) without any filler. Every word contributes to understanding the tool's purpose, making it highly concise and well-structured.

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 schema provides complete parameter descriptions and the purpose is clear, but the description does not explain behavioral aspects such as what happens if output_path is omitted, whether files are overwritten, or what return value is expected. With no annotations and no output schema, the description alone is not fully complete, though the schema mitigates some gaps by defining all parameters and defaults.

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 descriptions cover 100% of parameters, establishing a baseline of 3. The tool description adds no extra meaning beyond what the schema already provides—it only restates the formats and quality option, which are already documented in the input schema. It does not clarify any relationships between parameters or default output behavior.

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 uses the specific verb 're-encode' with the resource 'video' and explicitly lists target container formats (mp4, webm, mov, mkv), making the purpose unambiguous. This clearly distinguishes the tool from sibling tools like trim_video or resize_video, which operate on different aspects of video processing.

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 offers no guidance on when to use this tool versus alternatives such as compress_video or resize_video. It does not mention use cases, exclusions, or provide any comparison, leaving the agent to infer usage solely from the tool name and listed formats.

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