arcane_prune_volumes

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

With no annotations, the description must carry the full burden of behavioral disclosure. 'Prune' implies deletion, but the description does not explicitly state that volumes will be removed, how 'unused' is determined, or whether the action is irreversible. It lacks details about side effects or safety checks.

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 a single, direct sentence with no unnecessary words. It is perfectly concise and well-structured for its minimal content.

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?

Despite the tool having only one parameter, it is a destructive prune operation with no annotations or output schema. The description lacks definition of 'unused volumes', what happens to them, and potential impacts on containers or data. This leaves important gaps for an agent to safely invoke the tool.

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 coverage is 100% for the single parameter environmentId, which is described as 'The environment ID'. The description's 'in an environment' simply echoes the parameter, adding no new semantics. Baseline 3 is appropriate as the schema already documents the parameter.

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 uses the specific verb 'prune' with the resource 'unused volumes' and scopes it 'in an environment'. This clearly distinguishes it from sibling prune tools like arcane_prune_images and arcane_prune_networks by explicitly naming the target resource.

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 provides no guidance on when to use this tool versus alternatives. It does not mention cleanup contexts, how it differs from arcane_remove_volume or arcane_prune_system, or any prerequisites. There is no implied usage beyond the basic statement.

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