snapshot_list

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

The description discloses that the result reports `returned`, `limit`, and `truncated` to indicate capped reads, and it marks itself as a read operation. Without annotations, this provides good behavioral context. However, it does not mention potential side effects, permission requirements, or error states.

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 extremely concise: a single-line purpose followed by a numbered list of arguments. Every sentence is informative with no fluff. The [READ] prefix front-loads the operation type.

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 read-only list operation with 3 parameters and no output schema, the description covers the key points: purpose, parameter semantics, and simple pagination behavior. However, it could mention how to use the returned snapshot extIds with sibling tools like snapshot_delete or snapshot_restore, which would improve completeness.

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 input schema has 0% description coverage, but the description fully explains each parameter: vm_ext_id (returned by vm_list), limit (default 500, with pagination awareness), and target (optional). This adds essential meaning 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 clearly states it lists a VM's snapshots with specific fields (extId, name, createTime) and hints at the 'spot lingering snapshots' use case. It uses a clear [READ] tag and verb+resource structure, distinguishing it from sibling tools like snapshot_create, snapshot_delete, and snapshot_restore.

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 provides clear context (listing snapshots for a VM) but does not explicitly state when not to use this tool or compare it to alternatives such as recovery_point_list or protection_domain_list. There is no guidance on prerequisites or fallback tools.

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