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 and explicitly discloses a key behavioral trait: it does NOT click the final Generate button, stopping at ready-to-generate. This is a non-obvious limitation that prevents misuse, making the description highly 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?

The description is two sentences long, front-loaded with the main purpose in the first sentence and the crucial caveat in the second. Every sentence earns its place with no fluff.

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?

The description covers the core function and a critical limitation, and the schema fully documents parameters. It could optionally mention prerequisites like being connected to Google Flow (sibling tools include flow_connect), but overall it is adequately complete for a setup tool.

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 input schema provides 100% coverage for all 7 parameters, so the description's additional mention of 'Omni Flash or Veo model' aligns with the schema but adds minimal meaning beyond it. The description does not elaborate on other parameters like campaign or reference_images, but the schema already documents them, so baseline 3 is appropriate.

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 purpose: 'Set up a video generation in Google Flow.' It specifies the actions (fills prompt, selects model, configures settings) and distinguishes it from related tools like flow_generate_image by focusing on video setup.

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 clear context for when to use this tool (to set up a video generation) and implies it is a preparatory step without triggering the final generation. However, it does not explicitly mention alternatives or exclusions relative to sibling tools.

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