video_preview

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

No annotations are provided, so the description must carry the full burden. It discloses that the preview is fast and low-resolution, but it does not mention behavioral traits such as whether the original video is modified, output format, performance characteristics, or any side effects. The description lacks sufficient behavioral context for safe tool selection.

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: one sentence for the purpose followed by a clean, structured argument list. Every sentence earns its place with no redundancy or fluff.

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?

Given that an output schema exists, the description does not need to detail return values. It covers the tool's purpose, key parameters, and basic behavior. However, it could be slightly more complete by mentioning output format or typical use cases, but overall it is sufficient for the tool's simplicity.

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 (context signals), meaning the raw schema provides no meaning beyond types and defaults. The description adds clear, concise explanations for all three parameters (input_path, output_path, scale_factor), including a default explanation for scale_factor. This fully compensates for the schema's lack of descriptions.

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 purpose: 'Generate a fast low-resolution preview for quick review.' It uses a specific verb (generate) and resource (preview), and it distinguishes itself among many video-processing siblings by focusing on low-resolution preview generation.

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 implies usage for quick review but does not explicitly state when to use this tool versus alternatives like video_trim, video_resize, or other video tools. No when-not-to-use or alternative recommendations are provided.

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