Generate Short Video

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

Annotations indicate readOnlyHint=false and destructiveHint=false, and the description adds the key behavioral trait that it returns a dry-run payload unless live=true. This is helpful but does not elaborate on other side effects, permissions, or limitations. No contradiction with annotations.

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 very short (two sentences) with no wasted words, which is good for conciseness. However, given the tool's complexity (14 parameters), it sacrifices necessary detail. It could be restructured to front-load the key behavior while adding parameter hints.

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 14 parameters, no output schema, and no parameter descriptions, the description is grossly incomplete. It does not explain response format, provider options, size constraints, or how to use the generated payload. For a video generation tool, this leaves major gaps.

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 0%, meaning the schema provides no parameter descriptions. The description only explains the 'live' parameter and env var, ignoring the other 13 parameters. For a tool with many parameters including enums, this is insufficient to guide correct usage.

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 it generates a vertical video, providing a specific verb and resource. However, it does not differentiate from sibling tools like short_video_build_payload or short_video_agent_manifest, which may have overlapping purposes.

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 explains the dry-run behavior and how to enable live generation via 'live=true' or env var, offering some usage context. However, it gives no guidance on when to use this tool versus siblings, nor any prerequisites or exclusions.

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