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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered; the description's 'without changing anything' largely restates it. Genuine additions are the visibility scope (personal/team generations) and the archived-items note, but preview-vs-full-content merely mirrors the include_content parameter.

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?

Two sentences, with the use-case triggers front-loaded and the read-only constraint second. No filler, though the second sentence spends words on read-only behavior the annotations already declare.

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?

For a read-only list tool with no output schema, the description plus full schema coverage give an agent enough to call it correctly: triggers, scope of visibility, and archive/preview options. It is slightly thin on how results are paged and what the listing returns, but the parameters carry that load.

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 five optional parameters (page, type, archived, per_page, include_content) are already documented in the schema. The description adds no format, enum, or pagination detail beyond that, so baseline 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 (lists generations) and scopes it to visible personal/team generations, so an agent can distinguish it from write siblings like archive-generation or restore-generation. It stops short of explicitly contrasting with the two closest siblings, get-generation (single item) and list-generators (generators rather than outputs).

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 opening clause gives concrete triggers — find generated outputs, generation history, previous results, archived items, IDs for later generation actions — which is clear contextual guidance. It never states when to prefer get-generation or list-generators instead, so it stops at clear context rather than full alternative routing.

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