list_snapshots

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

With no annotations, the description carries the full behavioral burden. It discloses that the operation is read-only, that results are newest first, and that unparseable files are listed with their error rather than hidden. This is strong, though it could also mention pagination behavior or result size limits.

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?

Two sentences deliver a lot: the operation, ordering, included fields, workflow relevance, error handling, and safety. Every clause earns its place and the key behavior is front-loaded.

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 simple list tool with one optional parameter and a full output schema, the description is complete. It explains sorting, error visibility, read-only behavior, and how the output feeds into the broader snapshot workflow.

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 only parameter, limit, is fully documented in the schema with a default, bounds, and description. The tool description does not add further parameter details, but since schema coverage is 100%, the baseline of 3 is appropriate.

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 begins with a specific verb and resource — 'List the snapshot documents already in the snapshot directory' — and even specifies ordering and content. It also differentiates from the sibling compare_snapshots by explaining this tool is what determines whether an earlier snapshot exists and what from/to values to use.

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?

It gives clear workflow context: use this to see what snapshots exist, check for an earlier snapshot, and decide the from/to names for comparison. It does not explicitly name alternatives or say 'use compare_snapshots instead', but the role is clear enough from the comparison-oriented sentence.

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