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

Annotations already declare the safe read-only/idempotent profile, but the description adds real behavioral context: result ordering, the meaning of each lifecycle status value (including that 'generating' means asynchronous background work), and per-row fields. With no output schema, this disclosure of return semantics is genuinely load-bearing.

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?

Front-loads purpose and ordering before filters and return shape, with no filler sentences. It is dense and slightly run-on in the return-field enumeration, but every clause carries usable information.

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?

No output schema exists, so the description must carry return-value semantics, and it does — row fields, status meanings, and where to get full content. Combined with 100% schema coverage for inputs, an agent has everything needed to call and interpret this tool.

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 all three filters and the limit bounds are already documented in the schema. The description restates the filters and the 1-50/default-20 range without adding format or selection nuance beyond what the schema provides, so the baseline of 3 applies.

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 past generations') plus the sort order ('most recent first'), which is scope information an agent needs. It also distinguishes itself from get_generation by naming that sibling for full-content retrieval.

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?

Explicitly routes the agent to get_generation when full content is needed, which is a concrete when-to-use-vs-alternative condition. It stops short of saying when not to use this tool (e.g. browsing vs. targeted retrieval across unrelated list_* siblings), so it is clear but not exhaustive.

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