pdm_pve_lxc_snapshot_delete

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

No annotations provided, so description must carry behavioral disclosure. It states irreversibility but fails to mention the 'confirm' parameter's role, permissions needed, or any side effects beyond deletion. For a mutation tool, this is insufficient.

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?

Description is extremely concise (two sentences) but lacks essential details to be effective. While no fluff, the brevity compromises completeness.

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 the tool's complexity (delete on remote, multiple params, irreversible), the description is insufficient. It does not explain the confirm parameter, how to specify remote/vmid/snapname, or the return output. Sibling tools are similarly brief but for a destructive action, more context is needed.

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' explained). The tool description adds no parameter meaning beyond the schema, leaving three required params (remote, vmid, snapname) underexplained. Should compensate for low coverage.

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 'delete a container snapshot on a PDM-registered remote' with specific verb and resource. Distinguishes from sibling tools like pdm_pve_lxc_snapshot_create and pdm_pve_lxc_snapshot_rollback.

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?

Description labels tool as 'MUTATION' and 'Irreversible; no UNDO', implying destructive use. However, it lacks explicit guidance on when to use or when not, and does not mention alternatives among sibling tools.

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