delete_snapshot

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

No annotations are provided, so the description bears full responsibility. It discloses that deletion is safe for the running guest, frees disk, and returns a task UPID, but does not mention permissions, irreversibility, or potential side effects like cascading deletes.

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 two sentences, highly concise, with the key action and effect front-loaded. No unnecessary words or 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 4 required parameters and no output schema, the description is incomplete. It lacks parameter explanations, does not specify the output format beyond 'UPID', and provides no guidance on prerequisites or error handling.

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 must add meaning but only minimally explains 'name' and lists other parameters without definitions. It does not clarify the roles of 'node', 'vmid', or 'type' beyond stating they are needed.

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 (delete) and resource (snapshot by name), and explains the effect: frees disk usage without affecting the running guest. It distinguishes effectively from siblings like `create_snapshot` and `rollback_snapshot`.

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 mentions required parameters ('Needs node, vmid, type') but does not provide explicit guidance on when to use this tool versus alternatives like `rollback_snapshot` or `list_snapshots`. Usage is implied but not fully directed.

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