Rollback to snapshot

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

Annotations already indicate destructiveness, and the description adds that the VM/container will be stopped first and explicitly warns 'DESTRUCTIVE — ask the user to confirm', which adds behavioral context beyond annotations.

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?

Two sentences with no redundancy; the action is front-loaded, and critical behavioral notes follow efficiently.

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?

While the description covers the core action and key side effects (stop, destruction), it lacks details on error cases, vm_type differences, and confirmation parameter semantics, making it adequate but not comprehensive for a 5-parameter destructive tool.

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?

With 40% schema description coverage, the description fails to compensate by explaining parameters like node, vmid, or confirm, leaving required parameters undocumented beyond their names.

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 verb 'Revert' and the resource 'a VM or container to a previous snapshot state', making the tool's purpose distinct from sibling tools like create_snapshot or delete_snapshot.

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 provides useful context (stops the VM first, is destructive, requires user confirmation) but lacks guidance on when to use vs alternatives like restore_backup, or prerequisites like snapshot existence.

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