rollback_vm_snapshot

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

The description discloses the destructive consequence ('current state will be lost') without annotations. It adds value beyond the tool name, though it could mention whether the snapshot is preserved after rollback.

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 short, includes a warning, and front-loads the purpose. It is appropriately sized for the tool's simplicity.

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 simple action and required parameters, the description is mostly adequate but lacks information about output, error handling, or whether the snapshot remains available.

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 0% schema description coverage, the description must compensate but only lists parameter names (node, vmid, snapname) without additional meaning like format or examples. This barely adds value over the 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 the verb (rollback) and resource (VM snapshot) and explicitly warns that current state will be lost. It distinguishes from sibling tools like create_vm_snapshot and delete_vm_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 lacks explicit guidance on when to use this tool versus alternatives like rollback_container_snapshot. It implies usage for reverting VM state, but no exclusions or comparisons are provided.

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