compress_video

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

No annotations are present, and the description only lists parameters and a vague return statement ('compression result info'). No disclosure of side effects, error behavior, or hardware acceleration implications.

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?

Structured as a docstring with Args and Returns, but slightly verbose with Chinese translations. Purpose is front-loaded, but no extraneous content.

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?

Explains all parameters but lacks detail on return values, error handling, or behavioral trade-offs between quality and target_size_mb. Incomplete for a tool with 6 parameters.

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?

With 0% schema coverage, the description adds meaningful explanations for each parameter (e.g., quality choices, optional output path), compensating well for the schema's lack of detail.

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 'compress video file' and lists parameters, but it does not distinguish from the sibling compress_video_with_qsv, leading to ambiguity about when to use each.

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 on when to use this tool vs alternatives like compress_video_with_qsv or other video tools. No prerequisites or context provided.

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