list_checkpoints

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only reveals location and ordering, and does not state that the operation is read-only or side-effect free, what the returned entries look like, or how limit affects the result. For a listing tool this leaves the return semantics ambiguous.

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 text is very short with no filler and places the key ordering detail at the end. However, it is a noun fragment rather than a complete instruction, and the brevity shades into under-specification.

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 tool with no output schema and no annotations, the description should clarify what the returned checkpoint list contains and whether its entries can be passed to restore_checkpoint. The current text only says the items are on disk and newest first, leaving the payload shape and downstream usage to inference.

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%, and the description does not mention the limit parameter at all. Although the schema provides type, default, minimum, and maximum, the description should compensate for the low coverage by noting that limit controls how many checkpoints are returned; it does not.

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 identifies the resource (checkpoints on disk) and the ordering (newest first), so an agent can tell this is a listing operation. It lacks an explicit verb, but the tool name 'list_checkpoints' supplies it. It does not distinguish itself from restore_checkpoint or create_checkpoint, but the resource and ordering are specific enough.

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?

There is no guidance on when to use this tool versus alternatives like restore_checkpoint, create_checkpoint, or undo/redo. The phrase 'on disk' hints at persistent checkpoints, but the description never explains that this tool should be used to discover available restore points or how it fits into a checkpoint workflow.

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