vm_snapshot_rollback

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

With no annotations, the description carries full burden. It discloses irreversibility, that changes are discarded, no undo token, and the need for confirmation. Could mention resulting VM state but is sufficient.

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?

Highly concise: a clear header, warning, dry_run note, and bulleted args list. Every sentence adds value, no filler.

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 purpose, behavior, parameters, and usage guidance. Could be slightly more complete with post-rollback state, but given no output schema, it is sufficiently informative for an agent.

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 0%, so description fully compensates. Explains each parameter: vmid is numeric Proxmox ID, name references vm_list_snapshots, dry_run preview, target from config, node auto-locate. Adds meaningful context beyond 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?

The description clearly states 'Roll a VM back to a snapshot' with an explicit verb and resource. It distinguishes from sibling tools like vm_snapshot_create and vm_snapshot_delete by focusing on 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?

Provides strong usage guidance: warns of irreversibility, requires user confirmation, suggests dry_run preview, and references vm_list_snapshots for valid snapshot names. Lacks explicit 'when not to use' but implies caution.

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