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

Annotations already establish readOnly, idempotent, non-destructive behavior, so the description's added value is the operational context: signed links expire after 24 h, failed generations are refunded automatically, and the call is free. These are genuine traits an agent needs for retry and cost decisions, though polling cadence or link consumability is not addressed.

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?

One dense sentence front-loads the resource and return contents (status, then links), with refund and pricing caveats appended as short clauses. Every clause carries information; nothing is redundant with the name or title.

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?

With no output schema, the description must describe the return value and it does: status enumeration plus signed 24-hour links. Combined with the refund and free-cost notes for a single-parameter read tool, an agent has everything needed to call and interpret it.

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% and the generation_id field is documented as coming from studio_generate, so the schema carries the parameter semantics. The description adds no format, length, or sourcing detail beyond that, making the baseline 3 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 and resource ('Get an AI Studio generation') and immediately enumerates what is retrieved: status states and signed output links. The 'get' vs 'generate' contrast with the sibling studio_generate is implicit but unambiguous, and the status lifecycle makes the resource concrete.

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 status progression (queued → running → complete | failed) implies this is a polling tool to call after studio_generate, but the description never explicitly says when to call it or when to stop polling. No alternatives are named or excluded, so usage must be inferred.

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