snapshot_delete

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

Discloses write operation, high risk, irreversibility, audit record capture, and no undo. Without annotations, this covers essential behavioral traits.

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?

Concise and well-structured: summary line with risk, then parameter descriptions. No wasted sentences.

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?

Fully covers the delete operation, its risks, parameter usage, and audit behavior. Adequate for a 3-parameter tool without output schema.

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?

Adds significant meaning beyond schema: snapshot_id from snapshot_list, dry_run as preview, target as Xen Orchestra target. Compensates for 0% schema description coverage.

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?

Clearly states it deletes a VM snapshot by UUID, with explicit irreversibility. Differentiates from sibling tools like snapshot_list, snapshot_create, snapshot_revert.

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?

Explains source of snapshot_id (from snapshot_list), dry_run for preview, and default target behavior. Could explicitly mention when not to use, but context is clear.

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