List volume snapshots

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

There are no annotations, so the description carries the burden of behavioral disclosure. It surfaces a non-obvious behavioral fact: listing snapshots here requires write access and is volume-scoped. It does not describe output shape or error behavior, but for a list operation the key behavioral risk is addressed.

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 sentences with no wasted words: the first packs scope, permission, and the alternative, while the second adds a documentation link. Key information 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 one-parameter list tool with no output schema, the description covers the access requirement, the correct alternative, and the volume-scoped behavior, and it links to documentation. The exact return format is left unstated, but this is a minor gap for a simple list operation.

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 schema has a single `name` parameter with 0% description coverage, and the description does not explicitly state that `name` is the volume name. However, the phrase 'for a volume' plus the tool name makes the parameter's purpose reasonably inferable, adding only minimal semantic value beyond the schema.

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 action ('List snapshots for a volume via the volume-scoped action') and clearly identifies the resource and scope. It also distinguishes this tool from the global snapshot_list, so an agent can tell them apart.

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 explicitly names the alternative `snapshot_list` and gives the selection condition: use it for read-only introspection. It also warns that this tool requires write access, giving direct when-to-use and when-not-to-use guidance.

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