qemu_snapshot_delete

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

Annotations already mark destructiveHint:true, but the description adds that the VM remains locked by this session and must be unlocked after deletion. This discloses lock-holding behavior and cleanup requirements, which is context beyond what the annotations alone provide.

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 long, starts with the action and resource, and includes the lock/unlock note without any wasted words. Every sentence earns its place.

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 destructive delete operation with no output schema, the description covers the key precondition (VM stopped), the lock state, and the unlock follow-up. It is concise but sufficiently complete for this tool's complexity.

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 two required parameters with no descriptions (schema coverage 0%), and the description does not explain them. The only hint is 'named snapshot' which maps to the 'name' parameter, but vm_id remains implicit. The description does not compensate for the lack of schema descriptions.

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 verb 'Delete' with a specific resource 'named qcow2 internal disk snapshot' and a clear precondition 'while the VM is stopped.' This clearly distinguishes it from sibling tools like qemu_snapshot_create and qemu_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 explicitly states the condition under which to use the tool (VM stopped) and the required follow-up action ('call vm_unlock when finished'). While it doesn't explicitly mention alternatives, the stop condition and unlock instruction provide clear usage context.

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