volume_snapshot_list

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

With no annotations, the description carries full burden. It only states the action 'List' without disclosing whether the operation is read-only, whether it requires special permissions, or what the return format is. This is a minimal behavioral disclosure, no more than the tool name implies.

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, clear sentence with no fluff. It is front-loaded and appropriately sized for a tool with one parameter. It could be slightly more informative, but as concise phrasing it works well.

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 is simple with one required parameter and no output schema, so a brief description may suffice. However, it lacks any context about return behavior, pagination, or operational notes. It is minimally viable but leaves the agent without additional context to handle edge cases.

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 100% for the 'region' parameter, so the schema already defines it. The tool description adds no extra meaning beyond restating 'in a region', which is redundant. Baseline 3 applies because the schema handles parameter documentation.

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 uses a specific verb 'List' with a clear resource 'volume snapshots' and a scope qualifier 'in a region'. This distinguishes it from sibling tools like volume_list or volume_info, which address volumes but not 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 implies usage when you need to list volume snapshots for a region, but it provides no explicit guidance on when to choose this over alternatives or any exclusions. The context is minimal and relies on the tool name to convey intent.

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