delete_vm_snapshot

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

Adds 'Irreversible' beyond annotations (destructiveHint=true), providing stronger behavioral context. Also mentions a requirement, which is helpful. However, doesn't disclose potential side effects or permissions beyond the risk level.

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?

Extremely concise with three short sentences. Front-loaded with the main purpose, followed by key warnings. 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?

With an output schema and annotations, the description adequately covers the core action and important behavioral traits. Could mention that it permanently removes the snapshot to differentiate from rollback, but not necessary for a simple delete operation.

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 covers all three parameters with descriptions (100% coverage), so baseline is 3. Description does not add any parameter-specific details 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?

Description explicitly states 'Delete a VM snapshot', specifying the verb and resource, and distinguishes from sibling tools like delete_container_snapshot by mentioning VM.

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?

No explicit when-to-use or alternatives mentioned, but it provides a prerequisite ('Requires PROXMOX_RISK_LEVEL=all'). The purpose is clear enough to infer usage, but lacks guidance compared to rollback or list operations.

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