vm_snapshot_delete

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

With no annotations, the description explicitly labels the tool as '[WRITE]' and warns 'Destroys a rollback point — no undo', fully disclosing its destructive nature.

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 concise and front-loaded with the purpose. The Args section adds structure, but could be slightly tighter without losing clarity.

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 tool with no output schema, the description lacks explicit mention of return values or success/failure indicators. This is a notable gap given the 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?

Schema coverage is 0%, but the description explains all five parameters with practical details: vmid type, name source, dry_run preview, target config reference, and node auto-location behavior.

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 'Delete a named snapshot from a VM', identifying the action and resource. It distinguishes from sibling snapshot tools (create, list, rollback) and warns about destruction.

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?

It explains dry_run for preview and references vm_snapshot_list for available names. However, it does not explicitly mention when to prefer alternatives or avoid this tool (e.g., irreversible action).

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