pdm_pve_qemu_snapshot_delete

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

With no annotations provided, the description fully discloses behavioral traits: the operation is a mutation, irreversible, and has a dry-run safety mechanism. There is no contradiction with annotations (none exist). The warnings are explicit and comprehensive.

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 extremely concise—one sentence—with all critical information front-loaded (MUTATION, delete, irreversible, dry-run). Every part serves a clear purpose without any wasted words.

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?

The tool has an output schema (present but unseen) and a moderate number of parameters. The description covers essential safety warnings and dry-run behavior, but omits prerequisites (e.g., snapshot existence, permissions) and details about the return value. Overall, it is sufficient for a mutation tool with clear behavior.

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 only 20% (only 'proximo_target' has description). The tool description does not explain any parameters, relying on their names. While some parameters are self-explanatory (vmid, snapname, remote, confirm), the lack of details on format or constraints means the description adds minimal value 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 clearly states the action (delete a VM snapshot), the resource (VM snapshot), and the context (PDM-registered remote). It explicitly distinguishes from sibling snapshot tools (create and rollback) by specifying deletion and noting irreversibility.

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 includes a crucial usage detail: 'Dry-run by default,' implying that to perform an actual deletion, the 'confirm' parameter must be set to true. While it doesn't explicitly list when to use versus alternatives, the purpose is clear and the dry-run guidance is helpful for safe operation.

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