vm_delete_snapshot

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

Annotations indicate destructive and non-read-only behavior. The description adds concrete details: consolidates delta disk, works while VM is powered on, irreversible, audited to audit.db, and does not change current VM state. No contradictions with 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?

The description is front-loaded with the action label and core effect, then contrasts with sibling, gives usage tips, warnings, and parameter details in a structured Args list. Every sentence adds value 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?

Given the tool's complexity (destructive, multi-parameter, output schema exists), the description covers behavior, preconditions, side effects, safety, parameter details, and return format. It is fully self-contained and requires no external references.

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 has 0% description coverage, so description carries full burden. It provides detailed meaning for all 4 parameters: vm_name (exact name), snapshot_name (exact from vm_list_snapshots), remove_children (default false, meaning kept/consolidated, true deletes subtree), target (optional). Every parameter is clearly explained.

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 the tool deletes a named snapshot permanently and consolidates its delta disk. It distinguishes itself from vm_revert_snapshot by noting it does not change the VM's current state. The purpose is specific and unambiguous.

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 explicit guidance: use to permanently delete a snapshot, run vm_list_snapshots first for exact names, warns about irreversibility and need for user confirmation, and contrasts with vm_revert_snapshot. Alternative methods and prerequisites are fully covered.

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