autoflow_generate

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does add one genuinely useful trait — 'queued sequentially' — which tells the agent that calls are enqueued and processed in order rather than run concurrently. However, it does not disclose whether the call blocks until completion or returns immediately, what it returns (e.g., a job ID), failure/timeout behavior, or the download implications of autoDownloadResourceQuality.

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?

A single ~25-word sentence where every phrase earns its place: action, platform, models, mechanism, and queuing behavior. The main action is front-loaded, and there is zero filler or repetition of schema content.

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?

This is a complex tool — 9 parameters, asynchronous generation, no annotations, and no output schema — yet the description is a single sentence. It never mentions what to expect after invocation (immediate return vs. blocking, job references), how to monitor the queued job (despite autoflow_get_queue and autoflow_status existing as siblings), or the auto-download workflow. The 100% schema coverage mitigates the parameter-side gap, but the workflow-side gaps remain significant.

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 description coverage is 100%, so the baseline is 3; every parameter already has a meaningful description and enums where applicable. The description loosely maps to parameters ('Veo 3 or Nano Banana' → model, 'video or image' → mode), but it adds no syntax, defaults, or format details beyond what the schema already provides.

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 states a specific verb ('Generate'), a clear resource ('AI video or image on Google Flow'), the relevant models ('Veo 3 or Nano Banana'), and the mechanism ('via the Autoflow extension'). It is immediately distinguishable from all siblings, which are queue/status/management tools (autoflow_status, autoflow_get_queue, autoflow_clear_queue, etc.) — an agent can tell this is the content-creation tool without opening the schema.

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 phrase 'queued sequentially' implies a queue-based workflow, which loosely suggests that sibling tools like autoflow_get_queue or autoflow_cancel manage the resulting jobs. However, the description never explicitly states when to use this tool vs. its queue-management siblings, nor does it say when not to use it. Usage context is implied rather than stated.

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