List Snapshots

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

The description adds valuable behavioral context beyond the annotation: it discloses the sorting order and the exact return fields (filename, path, creation time, size). The readOnlyHint annotation already signals safety, and the description enriches that with specifics.

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, focused sentence that conveys the essence: what it does ('List all saved local snapshots'), ordering ('newest first'), and output (four specific fields). No filler or redundancy.

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 tool has no parameters and no output schema, so the description carries the full burden. It mentions the sorting, the scope ('all'), and the exact return fields, making the tool's behavior and results fully predictable.

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?

With zero parameters and an empty schema, the description necessarily carries no parameter info, but baseline 4 applies per the rubric. The description's mention of return fields gives a sense of what the tool operates on, which is sufficient.

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?

Purpose is explicitly stated with a specific verb and resource: 'List all saved local snapshots'. It also specifies the ordering ('sorted newest first') and distinct return fields, clearly distinguishing it from sibling tools that create, export, restore, or set up snapshots.

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 clearly implies when to use this tool: whenever you need to list snapshots. It doesn't explicitly mention exclusions or alternatives, but there are no other listing tools among the siblings, so the context is clear enough.

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