Delete snapshot

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

The description explicitly labels the tool as DESTRUCTIVE, which aligns with the destructiveHint: true annotation. It adds the instruction to ask for user confirmation, providing behavioral context beyond the annotation. This is sufficient for a simple deletion action.

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 extremely concise with two sentences: one stating the action and one providing a critical warning. Every sentence is necessary and earns its place.

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 simple deletion tool with no output schema and good annotations, the description is mostly complete. It covers the core operation and the destructive nature. However, it could mention that the snapshot must exist or that force and confirm parameters control behavior.

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 input schema has 6 parameters, but only 50% have descriptions. The tool description does not mention any parameters or provide additional meaning beyond the schema. Given the low schema coverage, the description should have compensated, but it fails to do so.

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 it 'Deletes a snapshot from a VM or container,' which is a specific verb+resource pair. It distinguishes itself from sibling tools like create_snapshot, rollback_snapshot, and list_snapshots by explicitly mentioning 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 a clear usage guideline: 'DESTRUCTIVE — ask the user to confirm before invoking.' This tells the agent when to use the tool (only after user confirmation) and implies a safety protocol. However, it does not provide explicit alternatives or exclusions.

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