convert_video_with_qsv

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

No annotations are provided, and the description lacks behavioral details such as whether the operation is destructive, what happens when output_path is null, rate limits, or permissions required. The description focuses on parameters but does not disclose the tool's side effects or return value structure.

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 concise, covering purpose and parameters in a single block with Args/Returns sections. It is front-loaded with the core purpose. No extraneous text. Slight improvement could be made by structuring parameter descriptions as a list for readability.

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 6-parameter tool with no output schema and no annotations, the description adequately explains parameter usage but lacks return value format details, error handling, hardware prerequisites, and behavioral context. Given complexity, it is partially complete but missing important contextual elements.

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 schema has 0% description coverage, so the description must compensate fully. It provides Chinese explanations for each parameter, including acceptable values for output_format, qsv_encoder, quality, and qsv_preset. This adds significant meaning beyond the bare schema types and defaults.

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 explicitly states '使用Intel QSV硬件加速转换视频' (Convert video using Intel QSV hardware acceleration), which is a specific verb+resource with technology identifier. It clearly distinguishes from siblings like convert_video_format (no QSV) and compress_video_with_qsv (compression instead of conversion).

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 mentions QSV hardware acceleration, implying it should be used when that acceleration is desired, but it does not explicitly state when to use this tool versus alternatives like convert_video_format or compress_video_with_qsv. No when-not-to-use or prerequisite conditions are provided.

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