Delete Parallels snapshot

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

The annotations already include destructiveHint=true, and the description adds that deletion is permanent, that delete_children removes descendant snapshots, and that confirm must be explicitly set to true. These details go beyond the schema and annotations without contradicting them.

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 compact and front-loaded: one sentence states the purpose, followed by a terse Args list. It contains no filler and avoids repeating schema titles.

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 4-parameter destructive tool, the description covers purpose, parameter semantics, and a safety requirement. The presence of an output schema means return-value details are not needed, and nothing critical appears missing.

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 documents all four parameters: vm and snapshot as name/UUID, delete_children with descendant semantics, and confirm as a mandatory explicit flag. This fully compensates for the lack of schema-level 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 'Permanently delete a snapshot to free host disk space,' using a specific verb and resource and clearly stating the purpose. This differentiates it from sibling tools like snapshot_revert or snapshot_create, which have different operations.

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 phrase 'to free host disk space' establishes a clear use case, and the confirm parameter note adds an important precondition. It does not explicitly name alternatives or exclusions, but the context is sufficient for basic tool selection.

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