volume_remove

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

Adds beyond annotations: describes failure on container references, force behavior with data loss, and return type. Annotations indicate destructive, but description provides operational nuance.

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?

Concise: first sentence states purpose, then failure condition, alternative tool, parameter list. No wasted words, front-loaded.

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?

Covers all needed: purpose, failure mode, alternative, parameters, return value. Complete for a simple removal tool with adequate annotations.

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?

With 0% schema coverage, description fully explains both parameters: name (volume name) and force (with behavior detail). Adds meaning beyond bare schema types.

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?

Description clearly states 'Remove a single volume by name', specifying the action and scope. Distinguishes from sibling volume_prune by contrasting single vs bulk cleanup.

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?

Explicitly explains when to use (single volume removal) and when to use alternative (volume_prune for bulk). Also details failure condition and force option.

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