arcane_remove_volume

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

No annotations are provided, so the description must carry the full behavioral burden. It does not disclose whether removal is permanent, destructive, or reversible, nor what happens to the volume's data. The phrase 'from an environment' is ambiguous—could mean detach or delete—leaving the agent without critical safety information.

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 clear sentence with no redundant words. It is appropriately concise for the stated purpose, though it lacks important behavioral context that would make it more useful.

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 removal tool with no annotations or output schema, the description is too sparse. It omits side effects, irreversibility, and any prerequisites. The ambiguity between 'remove' and 'delete' further reduces completeness, leaving the agent uncertain about the tool's full impact.

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 already describes both parameters ('volumeName' and 'environmentId') with 100% coverage, so baseline 3 is appropriate. The description adds no additional parameter details or context beyond what the schema provides.

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 ('Remove'), the target resource ('a volume'), and the context ('from an environment'). This distinguishes it from sibling tools like 'arcane_prune_volumes' (bulk cleanup of unused volumes) and 'arcane_create_volume'.

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 such as 'arcane_prune_volumes' or 'arcane_remove_network'. It does not mention prerequisites (e.g., whether the environment must be stopped) or cases where this tool is preferred over other removal operations.

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