veo_get_1080p

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

No annotations are present, so the description must fully disclose behavior. It mentions getting a high-resolution version and the prerequisite, but does not clarify whether this operation is synchronous or asynchronous, if it incurs additional cost, or if it is idempotent. The description lacks details on side effects or system impact beyond the basic retrieval nature.

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 well-structured with a clear first sentence, then context, usage instructions, and returns. It is not overly verbose and each sentence serves a purpose. A small improvement could be condensing the 'use when' bullet points.

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 the high schema coverage, presence of an output schema, and simple parameter set, the description covers the essential context. It explains the default behavior, usage, prerequisite, and return value. It is adequate for the tool's complexity.

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?

With 100% schema coverage, the input schema already documents both parameters (model and video_id). The description does not add significant meaning beyond the schema; it only implies usage of video_id. 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: to get the 1080p high-resolution version of a generated video. It distinguishes from the default lower resolution and is unique among sibling tools like veo_extend_video and veo_text_to_video.

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 provides explicit when-to-use guidance: when needing higher resolution for production, after initial generation is complete, and for clearer output. It also specifies the prerequisite that the video must be in 'succeeded' state, which is crucial for correct invocation.

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