Undo recent writes

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

With no annotations, the description carries the behavioral burden. It discloses the important side effect that each restored snapshot is removed from the list. However, it does not explain whether restoration overwrites current state irreversibly, how newer snapshots are handled, or any permission requirements.

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, well-structured sentence. The core action comes first, the source for the optional id is provided, and the side effect is stated without any filler.

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 description covers the main action, the id source, and a side effect, which is solid for a simple tool. But it does not explain the 'steps' parameter explicitly, nor does it describe failure behavior or what happens to snapshots newer than the one being restored. Given there is no output schema and no annotations, these gaps leave some ambiguity.

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 0%, so the description must compensate for both parameters. It gives useful meaning for 'id' by tying it to list_snapshots, but the 'steps' parameter is only vaguely implied by 'snapshot(s)' and its role in controlling how many snapshots to restore is not stated.

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 uses a specific verb ('Restore') and resource ('snapshot(s)'), and clarifies the scope: snapshots taken before writes. It also distinguishes itself from list_snapshots by indicating it consumes an id from that listing rather than merely showing 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?

The description gives clear context: use this after writes to restore the newest pre-write snapshots, or provide a specific id from list_snapshots. It does not explicitly list exclusions or alternatives, but the intended timing and targeting are evident.

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