convert_video_format

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

No annotations are provided, so the description must bear the full burden. It merely says 'convert' without revealing whether the original video is modified, if a new file is created, quality implications, or authentication requirements. This lack of detail hinders correct invocation.

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 extremely concise (5 words) and to the point. It front-loads the core purpose. While it could include more detail, it avoids unnecessary words, earning a high score for conciseness given the tool's simplicity.

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?

With no annotations, no output schema, and only 2 parameters, the description is insufficient. It does not explain the return value (e.g., URL of converted video), processing time, or any side effects. A conversion tool typically requires more context to set expectations.

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 50% (video_url has a description, output_format does not). The description adds no meaning beyond the schema; it doesn't explain the output_format parameter or any constraints. For a tool with low coverage, the description should compensate but fails to do so.

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 'Convert video to a different format' clearly states the action (convert) and resource (video), distinguishing it from siblings like 'convert_image_format' and other video manipulation tools. However, it lacks specificity on what 'different format' means, though the schema's output_format enum provides that.

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?

No guidance is given on when to use this tool vs alternatives like merge_videos or speedup_video. There is no mention of prerequisites, limitations, or scenarios where this tool is inappropriate.

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