generate_video

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

Disclosures generation time (1-6 minutes) and model options, which adds value beyond the null annotations. However, lacks details on idempotency, authorization requirements, or error handling, which the description must cover given no 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?

Two sentences, front-loaded with main purpose, no wasted words. Efficiently conveys key capabilities and constraints.

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?

Covers the main use cases and important constraints (required prompt, optional image/last frame, model options). Lacks details on output format or error conditions, but given no output schema and null annotations, this is acceptable.

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 100%, so baseline is 3. The description adds minor context (e.g., generation time, modes) but the per-parameter descriptions in the schema are already comprehensive, so the tool description adds limited extra semantic value.

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 generates a video from a text prompt using Gemini Veo, lists specific capabilities (text-to-video, image-to-video, first+last frame interpolation), and distinguishes it from siblings like generate_image by focusing on video 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?

Provides explicit context on when to use different modes (imagePath for image-to-video, lastFramePath for interpolation) and available models, but does not explicitly contrast with alternatives or state when not to use.

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