vsphere_delete_snapshot

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

Beyond the destructiveHint annotation, the description explains data consolidation, the VM keeps current data, permission mode, waiting behavior, and that large snapshots can take long to consolidate. These details add significant context for safe invocation.

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 well-structured with a front-loaded purpose, a brief behavioral note, and an organized Args list. Every sentence adds value with no redundancy.

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 purpose, behavior, permissions, parameter semantics, wait/timeout concerns, and operational caveats. Given the output schema exists, return values need not be described, making this complete for a destructive snapshot-deletion 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?

Schema descriptions are absent (coverage 0%), but the description provides a full Args block explaining every parameter, including edge cases like snapshot being ignored when delete_all is set. This fully compensates for the missing schema 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 opens with 'Delete one snapshot, a snapshot subtree, or every snapshot of a VM,' clearly specifying the verb, resource, and scope. This distinguishes it from sibling snapshot operations like create, revert, and list.

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 states the permission requirement (destructive mode) and the operational scope (one, subtree, or all snapshots), which implies when to use the tool. It does not explicitly name alternatives, but the delete purpose is unambiguous and distinct from siblings.

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