flow_generate_video

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

With no annotations, the description carries the full burden. It discloses that the tool stops at 'ready-to-generate' and does not execute the paid generation, which is a key behavioral trait. It does not cover rate limits or auth, but the core behavior is transparent.

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 with no extraneous content. The first states the purpose, the second provides a critical caveat. Every word earns its place.

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 7 parameters and no output schema, the description covers the essential behavioral context. It could optionally explain project reuse logic, but the schema already describes that. Overall, it provides adequate completeness.

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 minimal value beyond summarizing what the schema already provides ('fills prompt, selects Omni Flash or Veo model, configures settings'). No additional parameter meaning is given.

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 action 'Set up a video generation in Google Flow' with specific verb and resource. It differentiates from siblings like flow_generate_image by specifying video generation, and includes a critical behavioral note about not clicking final Generate.

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 note explicitly states what the tool does NOT do (final Generate is a paid feature), guiding appropriate use. However, it does not mention alternatives or when to use siblings, so guidance is slightly incomplete.

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