vm_clean_slate

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

The description adds behavioral context beyond annotations: it powers off the VM first (if running) and reverts to the named snapshot. This supplements the destructiveHint and readOnlyHint annotations. The explanation is consistent and informative.

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 extremely concise and well-structured: a one-line summary, two sentences of behavior, then a brief Args section. No unnecessary words, and the key information is front-loaded.

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?

The description covers the main operation, preconditions, and use case. It does not detail error handling or timing, but an output schema exists. Given the complexity of a VM revert tool, the description is sufficiently 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?

With 0% schema description coverage, the description compensates by explaining the three parameters: vm_name (name of VM), snapshot_name (with default 'baseline'), and target (optional vCenter/ESXi target). This adds meaningful semantics that the raw schema lacked.

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 VM to its baseline snapshot, including the behavior of powering off first. It uniquely identifies the operation among siblings like vm_power_on or vm_rollback_plan. The explicit [WRITE] prefix further clarifies the action type.

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 advises using the tool to reset a lab/dev VM to a clean state after a task completes, providing clear use context. However, it does not mention when not to use it or explicitly compare to alternatives like vm_rollback_plan, which could cause confusion.

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