extend_video

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

No annotations provided. Description says it creates a task and returns task id, status, and output URLs, but omits that it requires a source_task_id, is asynchronous, and any side effects. Does not disclose that this is an extension of a previous video generation.

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?

One sentence is concise and front-loaded with the core purpose, but it omits essential details, making it under-specifying rather than optimally concise.

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 4 parameters with low schema coverage, no output schema, and no annotations, the description fails to explain the source_task_id dependency, behavior of wait/timeout/polling, or output structure, leaving large gaps for an AI agent.

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 coverage is only 25% with one parameter described. Description adds no meaning for source_task_id, timeout_ms, or poll_interval_ms, and does not explain how they relate to extending a video.

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 creates a Veo 3.1 task specifically for extending video, distinguishing it from siblings like text_to_video and upscale_video.

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 versus alternatives; no prerequisites or context for using extend_video over check_pricing, get_task, etc.

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