generations

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

With no annotations provided, the description carries full burden. It correctly indicates that list is read-only and rollback is a mutation (revert), but it lacks warnings about destructive nature, reversibility, or prerequisites. More transparency about side effects would be beneficial.

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 extremely concise at two sentences, yet covers the two main actions and the mode parameter with no redundant information. Every part adds value.

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?

Given the tool's simplicity (2 parameters, output schema exists), the description covers the primary use cases. However, it lacks details on edge cases (e.g., what happens during rollback if no previous generation) and does not mention relationship to sibling tools like switch. Slight gaps prevent a higher score.

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 has 0% description coverage, so the description adds significant meaning. It explicitly states valid values for action ('list' or 'rollback') and mode ('home-manager' for HM generations), and explains the effect of each. This fully compensates for the schema's lack of parameter descriptions.

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 two distinct actions: list (enumerate generations with dates and current marker) and rollback (revert to previous generation). It also mentions the mode parameter for home-manager. This distinguishes it from sibling tools like build, check, etc., which have different purposes.

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 provides context on when to use list vs rollback and mentions the mode parameter, but it does not explicitly tell when not to use this tool or compare with alternatives like switch or diff. More detailed usage context would improve this score.

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