Fetch a Veo video by operation

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

No annotations are provided, but the description carries meaningful behavioral weight: it discloses that the call blocks/waits on an in-flight operation, that it writes a video to disk, and that it incurs no additional cost. It does not cover failure modes — what happens if the operation already failed, is still pending past a timeout, or if the target file exists — which is the main remaining gap for a long-running write tool.

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?

Three short sentences, zero waste: purpose first, then the routing condition, then the cost reassurance. Front-loaded and easy to scan.

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?

For a 3-parameter tool with full schema coverage and no output schema, the description covers purpose, trigger, and cost adequately. It is slightly thin on what the agent gets back (saved file location/name) and on error behavior, but nothing blocks a correct invocation.

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 filename, operation, and outputDir are already fully documented in the schema. The description only reinforces where the operation string originates, adding no new semantics for the save path or filename parameters. 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?

States a specific verb pair and resource: wait on an already started Veo operation and save its video. It also distinguishes itself from the sibling generate_video by positioning itself as the recovery path for a failed render.

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?

Gives an explicit trigger condition — "use it when generate_video failed after the render had started" — and tells the agent where the required operation value comes from (its error). This implicitly excludes fresh generation, so the agent can route correctly without opening either schema.

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