pdm_pve_lxc_snapshot_delete

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

No annotations provided, so description carries full burden. Irreversible ('no UNDO'), dry-run by default, confirm=True executes and returns a PDM task reference. Also warns that pve_task_status cannot poll the PDM UPID, directing to pdm_tasks_list.

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?

Concise: one-line purpose, then behavior, then sibling references, then execution flow. Every sentence provides distinct value. Front-loaded with key action.

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?

Covers mutation nature, irreversibility, dry-run/confirm, tracking. Output schema present so return values are documented. Lacks explicit mention of permissions or prerequisites, but overall sufficient for a tool with 5 parameters and no annotation gaps.

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 3. Description mentions confirm and proximo_target but adds little beyond schema descriptions. No additional semantic detail for parameters.

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?

Opens with 'MUTATION: delete a named container snapshot on a PDM-registered remote, through PDM.' Clearly specifies verb (delete), resource (container snapshot), and context (PDM). Distinguishes from sibling tools like pdm_pve_qemu_snapshot_delete and pdm_pve_lxc_snapshot_create.

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?

Explicitly states when to use alternatives: 'For a VM snapshot use pdm_pve_qemu_snapshot_delete; to create rather than delete a snapshot use pdm_pve_lxc_snapshot_create.' Also explains the dry-run default and confirm behavior.

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