veo_generate_video

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

With no annotations, the description carries the full burden of behavioral disclosure, but it simply restates the tool's function. It does not mention the asynchronous/polling nature, duration limits, cost implications, authentication needs, or that the video is saved to an output path.

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 a single sentence, which is concise, but it is under-specified for a tool with 13 parameters and no other documentation. It lacks structured information or important front-loaded context (e.g., long-running operation behavior).

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?

Despite a rich input schema, the description gives no contextual guidance on how to invoke the tool correctly. It does not mention return values, error handling, or the operational workflow (e.g., polling until video ready). The tool is complex, but the description is extremely incomplete.

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 description provides zero additional context for the 13 parameters, and schema description coverage is 0%. It does not explain key details like how `image_path`, `last_frame_path`, or `reference_image_paths` affect generation, nor the meaning of `auth_mode`.

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 action ('Generate a video') and the specific resource ('Google's Veo 3.1 Gemini API'). It distinguishes the tool from siblings: `nano_banana_generate_image` generates images, `stitch_videos` stitches existing videos, but this generates videos from scratch.

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 gives no explicit guidance on when to use this tool versus alternatives. It implies use when generating a video, but there is no mention of prerequisites (e.g., API key), typical scenarios, or exclusions compared to sibling tools.

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