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

Annotations already guarantee readOnly/idempotent/non-destructive, so the bar is lower, and the description still adds real behavioral context: results are newest-first, pagination uses the returned nextCursor, links are signed and expire in 24h, and the call is free (no credit cost). Only the exact page-size default (10) lives in the schema rather than the prose.

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 dense sentence leads with the verb and resource, then tacks on ordering, payload, pagination, and cost in a tight clause chain with no filler.

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 carries the return-value burden and does so reasonably: it names status and signed links (with 24h validity) and the pagination cursor. It stops short of enumerating the full item fields, but for a list endpoint it is nearly sufficient.

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 schema already documents kind, limit, cursor, and status enums. The description only echoes the cursor/nextCursor round-trip and adds no filter syntax or format meaning beyond the schema, 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 ('List the account's AI Studio generations') plus the ordering ('newest first'), the payload ('status and signed output links'), and the pagination mechanism. This clearly distinguishes it from the sibling get_generation, which fetches a single generation.

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 implies listing usage and explains pagination flow via 'nextCursor', but never says when to prefer this over get_generation or list_projects, nor any preconditions. Usage 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.