Delete Snapshot

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

The description goes beyond annotations by explicitly warning that the snapshot and its state are permanently removed and cannot be undone. It also states the return value (confirmation message). This adds critical behavioral context for a destructive action, aligning with the destructiveHint=true annotation.

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: purpose statement, warning, argument list, and return value. Every sentence contributes necessary information with no redundancy. The warning is appropriately prominent.

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?

Despite lacking an output schema, the description states the return type (confirmation message). It covers the destructive nature, irreversibility, and required parameters. For a simple delete tool with good annotations and schema coverage, the description is 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?

The schema covers all parameters with descriptions (100% coverage), so the baseline is 3. The description repeats the two main parameters (vmx_path, snapshot_name) but does not add significant new meaning beyond the schema. The optional vm_password parameter is not mentioned in the description, but the schema covers it adequately.

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 ('Delete a snapshot') and the target resource ('from a VMware Fusion virtual machine'). It distinguishes itself from sibling tools like fusion_create_snapshot and fusion_revert_snapshot by specifying deletion.

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 provides clear context (delete a snapshot) and a warning, but does not explicitly mention when to use this tool versus alternatives, nor any exclusions. It implies usage through its direct action statement, which is sufficient for a straightforward delete operation.

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