Delete volume snapshot

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

With no annotations, the description carries the full behavioral disclosure burden. It explicitly warns the tool is 'Destructive' and instructs the agent to require explicit user authorization. However, it does not mention irreversibility, impact on downstream operations, or what happens after deletion.

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?

Three sentences with no filler: the action, the destructive warning, the authorization constraint, and a reference doc link. Important safety information is front-loaded, and every sentence 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 destructive tool with two string parameters and no output schema, the description covers the core purpose and safety gate. It is incomplete on parameter semantics and long-term effects, so an agent may still need external context before calling it correctly.

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 does not explain that 'name' refers to the volume and 'snapshotName' refers to the snapshot to delete. The phrase 'snapshot of a volume' hints at the relationship but does not compensate for the lack of parameter documentation.

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 states a specific verb and resource: 'Delete a snapshot of a volume.' This is clear and distinct from read/list operations, though it does not explicitly differentiate from sibling tools like volume_snapshot_purge or volume_snapshot_cr_delete.

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 gives explicit when-not guidance: do not call unless the user has explicitly authorized it in this conversation, and never proactively, speculatively, or as a side effect. It does not mention alternative tools or when a different snapshot operation would be preferable, so it stops short of a 5.

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