qemu_snapshot_list

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

Beyond the readOnlyHint and non-destructive annotations, the description discloses a critical side effect: the VM remains locked by the session and requires a call to vm_unlock. This is important behavioral context not captured in structured annotations.

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?

Two short sentences, front-loaded with the primary action and resource, followed by a necessary behavioral note. Every word earns its place with no redundancy.

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 (one parameter, no output schema), and the description covers the main constraint (stopped-VM), the safety profile (via annotations), and the lock side-effect. No critical gaps for the agent to invoke it correctly.

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?

Only one parameter (vm_id) exists with zero schema description coverage. The parameter name is self-explanatory, but the description does not explicitly mention it or add detail about how to specify the VM. It neither confuses nor significantly enhances the schema, landing at the minimum viable score.

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 'stopped-VM qcow2 internal snapshots', and the 'stopped-VM' qualifier distinguishes it from other snapshot operations. It clearly states what the tool does and helps differentiate from qemu_snapshot_create/restore/delete.

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 context that this tool is for stopped VMs and notes the locking behavior, implying it should be paired with vm_unlock. However, it does not explicitly name alternative tools or exclusion criteria, though the sibling snapshot tools are obvious alternatives.

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