qemu_snapshot_list

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

Annotations already cover the safety profile: readOnlyHint, idempotentHint, and non-destructive. The description adds useful context by restricting the scope to stopped VMs and qcow2 internal snapshots, but it does not disclose behavior such as error conditions when the VM is not stopped or what happens if no snapshots exist.

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 compact sentence with no filler or repetition. It front-loads the action and clearly scopes the resource type, which is appropriate for a simple one-parameter list tool.

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 low-complexity tool with one required parameter and strong read-only annotations, the description is mostly sufficient. It states the resource type and scope, though it would be slightly more complete if it noted that the return value is a list of snapshot names/metadata in the absence of an output schema.

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 0%, and the description does not mention vm_id at all. The schema provides only the name, requirement, and pattern, so the agent must infer that vm_id identifies the target VM. The description should have explicitly linked vm_id to the snapshot listing operation.

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 names a specific verb ('List') and resource ('stopped-VM qcow2 internal snapshots'), making the operation unambiguous. It also distinguishes itself from sibling snapshot-create/restore/delete tools by focusing on listing rather than mutating 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 'stopped-VM' qualifier implies the tool is for offline VMs, and the listing action implies it could be used before create/restore/delete operations. However, it does not explicitly state when to choose this tool over alternatives or when it should not be used, such as for running VMs.

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