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

Annotations already establish a safe, read-only, non-open-world operation, so the description only needs to add operational context. It does so meaningfully by disclosing the polling model and the fact that outputs are returned as signed URLs on completion, implying the result may be incomplete on early calls and that URLs are likely time-limited. It stops short of describing the in-progress response shape.

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 tight sentence with no filler, front-loading the action (poll) and the payoff (signed output URLs). Every clause 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?

There is no output schema, so the description must characterize returns; it does so by naming signed output URLs on completion. It is nearly complete for a simple one-parameter poll tool, with the only gap being the response shape when the generation is not yet finished.

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 0% for the single required generationId parameter, so the description must carry the load. It implies the parameter identifies the generation to poll, but adds no format, sourcing (e.g., from create_studio_generation), or error semantics beyond the self-evident UUID name.

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 and resource: polling one AI Studio generation and retrieving signed output URLs. It is clearly distinct from list_studio_generations and create_studio_generation, though it does not explicitly name those siblings to route the agent.

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?

"Poll" implies the intended workflow (call repeatedly until completion), and "when it completes" hints at the terminal condition. However, no alternatives are named and there is no explicit guidance on polling cadence or what to do if the generation is still in progress.

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