Delete Volume

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

Adds 'permanently' and detachment requirement beyond annotations. Annotations already indicate destructive and idempotent behavior; description reinforces and adds context without contradiction.

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?

Two concise sentences with no redundancy. Front-loaded with core action and immediately adds critical precondition.

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?

Sufficient for a simple delete tool with one parameter, no output schema, and annotations present. Covers action and precondition; could mention what happens if volume is attached (though implied).

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 covers 100% of the single parameter (id) with description. Description adds no additional meaning beyond schema, meeting the baseline for high 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 'Delete a volume permanently', identifying the specific verb and resource. Differentiates from sibling tools like create, attach, detach, and update volumes.

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?

Provides a clear precondition: 'volume must be detached from any server'. Implicitly guides when to use (when volume is detached) and hints at alternative (detach first if attached), though not explicitly stated.

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