List snapshots

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

No annotations are provided, so the description carries the full behavioral burden. It does reveal that snapshots are taken before writes, are returned newest-first, and expose IDs for undo. However, it does not explicitly state that listing is read-only or mention pagination/limits, though the verb 'List' conveys a safe read operation.

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 a single, information-dense sentence with no filler. It packs the snapshot policy ('taken before writes'), ordering ('newest first'), and purpose ('ids for undo') into a compact statement, and the title supplies the missing verb.

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 zero-parameter list tool with no output schema, the description covers the core facts an agent needs: what snapshots are, their ordering, and how their IDs relate to undo. It does not explicitly say it lists all snapshots or describe the response shape, but the complexity is low and the title/schema cover basic 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 input schema is empty with zero parameters, so there are no parameter semantics for the description to clarify. The description offers no parameter-level detail, but none is needed; the zero-parameter baseline of 4 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?

The title clearly gives the verb+resource ('List snapshots'), and the description adds that snapshots are pre-write, ordered newest-first, and carry IDs for undo. It is clear about what is retrieved, but it never explicitly differentiates itself from close siblings like undo, so it stops short of a 5.

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 phrase 'with ids for undo' implies this tool is the lookup step before using undo, but the description never states when to choose list_snapshots over undo or another sibling. There are no explicit when/when-not conditions or alternative tool names, so guidance is only implicit.

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