vm_delete_snapshot

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

Disclosure includes that it frees disk space, does not change VM state, consolidation can be slow, operation is irreversible, audited to audit.db, and async behavior with task IDs. This adds significant context beyond 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 well-structured with clear sections, but slightly lengthy. However, each sentence adds value, so it is only marginally penalized.

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?

Covers preconditions (run vm_list_snapshots), side effects (slow consolidation), error handling (returns not-found message), async behavior, and audit logging. Complete given the tool's complexity and available annotations.

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?

With 0% schema description coverage, the description fully explains all 5 parameters: vm_name, snapshot_name, remove_children (default and effect), wait (default and blocking behavior), and target (usage). Adds meaning beyond the schema.

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 action (Permanently delete a named snapshot) and the resource (snapshot). It distinguishes from the sibling vm_revert_snapshot by noting it does not change VM state, and references vm_list_snapshots for exact names.

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?

Explicitly explains when to use (to free disk space), contrasts with vm_revert_snapshot, advises running vm_list_snapshots first, warns about irreversibility and user confirmation, and explains async vs sync with wait parameter.

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