remove_volume

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

With no annotations provided, the description correctly discloses destructive behavior ('permanently lost') and a specific error condition (fails if in use). It does not address what happens if the volume doesn't exist, but the core behavioral traits are well communicated.

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: three short sentences plus an Args line. Every sentence adds essential information (purpose, consequence, failure condition, parameter). No wasted words.

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 one-parameter destructive tool, the description covers the key aspects: what it does, what it destroys, and when it fails. It does not describe the return value or confirmation, but given the output schema exists and the tool's low complexity, this is a minor gap.

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 0% description coverage, so the description must compensate. However, it only restates the parameter name ('volume_name: name of the volume to remove'), adding minimal meaning beyond the schema. It does not provide format constraints, examples, or additional context to fully clarify the parameter's usage.

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 the action ('Deletes'), the resource ('a Docker volume by name'), and includes a critical consequence ('Data stored in it is permanently lost'). This makes the tool's purpose unambiguous and distinctly different from sibling tools like delete_container.

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 explicitly states the tool's primary use (deleting a volume) and a key precondition ('Fails if the volume is currently in use by a container'). This provides clear context for when the tool can be used, though it doesn't mention alternatives or when not to use it beyond the failure case.

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