snapshot_revert

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

No annotations are present, so the description carries full burden. It discloses irreversibility, audit record, and the dry_run preview. However, it doesn't cover potential side effects like VM state or prerequisites, but the critical behavioral traits are well communicated.

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 concise and front-loaded with the risk tag and purpose. Each sentence serves a clear role: risk, action, guidance, parameter details. No fluff.

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?

For a simple tool with 3 parameters and no output schema, the description covers purpose, parameters, and usage well. It lacks mention of the return value or prerequisites like VM state, but remains largely complete.

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?

Despite 0% schema description coverage, the description provides meaningful explanations for each parameter: snapshot_id links to snapshot_list, dry_run explains preview behavior, target notes default omission. This adds significant value beyond the raw 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 action: 'Revert a VM to a snapshot.' It uses a specific verb and resource, and the risk tag '[WRITE][risk=high]' distinguishes it from siblings like snapshot_list or snapshot_create.

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?

Explicit guidance is provided: 'take a fresh snapshot first (snapshot_create) if you may need to come back' and 'declares no undo.' This helps the agent decide when to use the tool and what precautions to take.

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