pve_snapshot_delete

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

No annotations exist, so the description carries full burden. It discloses mutation, dry-run behavior, async nature, and consequences of deletion. However, it does not mention implications of the force parameter or required permissions, slightly limiting transparency.

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?

Two sentences convey purpose, consequence, usage, async follow-up, and sibling distinction. No redundant words; highly efficient.

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 7 parameters, 2 required, no annotations, and an output schema, the description covers key behavioral and usage aspects. It lacks details about the force parameter and does not explain the output schema, but the schema itself is detailed. Overall, well-rounded for 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 description coverage is 100%, so baseline is 3. The description adds no significant parameter semantics beyond the schema; it only mentions confirm=True for execution and ties to dry-run default. No extra meaning for other parameters like force, node, kind, snapname.

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 'MUTATION: delete a snapshot (removes a restore point) — you can't roll back to it afterward', specifying verb, resource, and consequence. It distinguishes from sibling pve_snapshot_create by explicitly mentioning creation as an alternative.

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: dry-run by default, confirm=True to execute, async returns UPID to poll with pve_task_status, and directs to pve_snapshot_create for creation. This covers when and how to use the tool.

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