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

Describes the state-changing nature, notes authorization requirement, and clarifies that it does not delete the generation. The annotation destructiveHint: false aligns with the description, so no contradiction exists.

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?

The description is succinct, with only two sentences that convey all essential information without redundancy. It is well-structured and easy to parse.

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?

The tool is simple with a single parameter, and the description covers the action, effect, prerequisites, and non-destructive nature. No additional context is needed for correct invocation.

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?

The schema already provides the parameter description, but the tool description adds 'from list-generations,' which gives valuable context on how to obtain the generation_id. This minor addition justifies a slight bonus.

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 clearly states the action (archive, hide, or remove) on a specific resource (generation) and its effect (removing from active list without deletion). It distinguishes from destructive actions by explicitly noting 'without deleting it'.

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?

Provides an explicit trigger condition ('when the user wants to archive, hide, or remove an existing generation from the active generation list') and clarifies non-destructive intent. Also mentions the prerequisite of calling list-generations, which serves as guidance.

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