pdm_pve_lxc_snapshot_rollback

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

No annotations are provided, so the description carries the full burden. It labels the operation as MUTATION and DESTRUCTIVE, and mentions the safety snapshot and dry-run behavior. However, it does not detail side effects on current state, reversibility, or permission requirements. The transparency is adequate but not 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 two sentences, uses bold markers for key terms, and is front-loaded with 'MUTATION'. Every word adds value, no fluff. Extremely concise.

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 has 5 parameters, no annotations, and an output schema (which reduces need for return value explanation), the description covers the core action and safety measures. But it lacks parameter details and usage context. It is minimally complete but has 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 coverage is only 20%, and the description does not explain any parameters beyond the overall action. It fails to clarify the meaning of 'vmid', 'remote', 'snapname', 'confirm', or 'proximo_target'. With low coverage, the description should compensate but does not, leaving agents without parameter guidance.

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: rolling back a container to a snapshot. The name 'pdm_pve_lxc_snapshot_rollback' is specific and distinct from sibling tools like snapshot_create or snapshot_delete. The description includes 'MUTATION' and 'DESTRUCTIVE' markers, further clarifying the operation.

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 'Dry-run by default' and 'Takes an auto safety-snapshot first', which imply cautious usage. However, it does not explicitly compare to alternatives like pve_rollback or specify when not to use this tool. The context of rolling back on PDM-registered remotes is clear but lacks explicit guidance.

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