vsphere_revert_to_snapshot

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

The description discloses major behavioral implications: later changes are discarded and everything written since the snapshot is lost. It also explains power-on suppression and waiting behavior, adding value beyond the destructiveHint annotation without contradicting it.

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 well-structured: a leading purpose statement, a critical warning, a permission note, and a clean Args list. No wasted words.

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's complexity and destructive nature, the description provides all essential context: operation, risk, prerequisites, parameter semantics, and task behavior. The presence of an output schema means return values need not be described. Complete and self-sufficient.

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 description coverage is 0%, but the description thoroughly explains every parameter, including accepted formats for vm (name/moid/UUID/path) and snapshot (name/path/moid), defaults, and the effect of suppress_power_on, wait, and timeout_seconds. This fully compensates for the schema's lack of descriptions.

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 tool reverts a virtual machine to a snapshot and discards later changes, which is a specific verb+resource+effect. This distinguishes it from sibling snapshot tools like create_snapshot and 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 clearly states a prerequisite (requires destructive permission mode) and explains default behavior for the snapshot parameter. It does not explicitly contrast with alternatives or say when not to use the tool, but the context is otherwise clear.

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