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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is known. The description adds real value beyond that: it spells out the irreversible consequence ('Destroys all data on the volume') and the operational prerequisite that the volume must be detached first, which the annotations cannot convey.

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 short sentences, zero filler, with the action and its precondition front-loaded before the destructive consequence.

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 one-parameter delete with no output schema, the description covers purpose, precondition, and consequence adequately. It omits only secondary details such as error behavior on a still-attached volume or whether deletion is recoverable.

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 single volumeId parameter has 0% schema description coverage and the description never mentions it, so no format or identification guidance is added. The parameter is trivially inferable from the tool name, so this is a minor rather than fatal gap.

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?

States a specific verb and resource ('Delete a volume') with a scope constraint ('Must be detached first') that immediately separates it from the sibling detach/list/create volume tools. An agent can pick it out without opening the schema.

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 precondition 'Must be detached first' gives clear when-to-use context and implicitly routes to the sibling detach tool. It stops short of explicitly naming that alternative or stating when deletion is discouraged, so it is clear but not fully prescriptive.

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