delete_snapshot

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

With no annotations provided, the description carries full burden. It discloses the destructive nature, irreversibility, and the preview/confirm behavior, which are critical behavioral traits. It could also mention prerequisites like VM existence, but for a delete tool, the key behaviors are covered.

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: it opens with a clear DESTRUCTIVE warning, states the function, notes irreversibility, and then lists parameters. Every sentence earns its place with no waste.

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?

Given the complexity of a destructive mutation tool with 3 parameters and no annotations, the description is remarkably complete. It covers the action, the irreversibility, the confirm requirement, and the preview behavior. The output schema can handle return value details, so the description need not explain further.

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%, and the description compensates fully by defining each parameter: vm_id and snapshot_id as identifiers, and confirm requiring true to execute with a preview otherwise. This adds meaningful context beyond the schema's bare titles.

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 'Delete a snapshot permanently' with a specific verb and resource. It distinguishes from sibling tools like list_snapshots, create_snapshot, and revert_snapshot by explicitly indicating 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?

It gives clear usage context by explaining the confirm flag must be true to execute and that otherwise a preview is returned. While it doesn't explicitly mention alternatives or when not to use, the context is clear and the confirm behavior serves as a safety guideline.

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