List snapshots

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

With no annotations provided, the description carries the full burden and does well by explicitly stating it is a 'plain read-only GET' and safe for use in '--read-only mode.' It does not disclose return format or potential performance implications, but for a zero-parameter list operation this level of disclosure is strong.

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 two short sentences with no filler. The core behavior and safety profile are front-loaded, and the documentation link is appended without disrupting the essential message.

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, parameterless read-only list tool, the description covers all the information an agent needs: what is listed, the scope, the safety profile, and where to find further documentation. No essential context appears to be missing.

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 tool has zero parameters, so there is no schema to compensate for, and the description reinforces this by framing the operation as global ('all snapshots across all volumes') with no filtering options. Per the baseline for zero-parameter tools, this 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 states a specific verb ('List'), a precise resource ('all snapshots'), and a scope ('across all volumes'), which clearly distinguishes it from volume-scoped snapshot tools like volume_snapshot_list. The title and description together make the tool's function unmistakable.

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 global snapshot listing across all volumes, which is distinct from per-volume snapshot tools, and explicitly notes it is available in read-only mode. It does not name alternatives or give a 'when not to use' rule, so it falls just short of the highest bar.

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