qemu_snapshot_delete

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

Annotations already mark the operation as destructive and non-idempotent. The description adds useful behavioral context beyond annotations by specifying the snapshot type (qcow2 internal disk snapshot) and the required VM state (stopped). This helps the agent understand preconditions and what will be affected.

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?

A single sentence with no filler. It front-loads the action, specifies the target object, and adds the key precondition. Every part 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 simple two-parameter destructive tool with annotations indicating destructive behavior, the description is largely complete: it states what is deleted and under what condition. It does not describe error cases or how to discover valid snapshot names, but those are not essential for basic invocation.

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?

Input schema coverage is 0%, so the description carries the burden of explaining parameters. It explicitly ties 'name' to the named snapshot and implies 'vm_id' through 'the VM is stopped', but it does not clarify parameter formats or relationships beyond what the JSON schema patterns already provide. Some meaning is added, but not enough to fully 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 action (delete), a specific resource (named qcow2 internal disk snapshot), and an important condition (while the VM is stopped). It clearly distinguishes this tool from sibling snapshot tools like qemu_snapshot_create, qemu_snapshot_restore, and qemu_snapshot_list.

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 gives a clear usage context by requiring the VM to be stopped before deletion. It does not explicitly mention alternative tools or list when-not-to-use conditions, but the precondition and the destructive nature are clear enough to guide basic selection.

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