remove_volume

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

States 'Destructive; requires confirmation token' which adds behavioral context beyond just 'remove volume'. However, no explanation of what happens if volume is in use, or the nature of the confirmation token.

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 short sentences, front-loaded with the main action. No unnecessary 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?

Lacks details on return values, error handling, or interaction with confirmation mechanism. No output schema, so description should provide more context about outcome.

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?

Only addresses the 'name' parameter implicitly ('by name'). The other three parameters (force, env_id, agent_token) are not explained in the description. Schema description coverage is 0%, so description fails to compensate.

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 the action ('Remove a volume by name'), resource ('volume'), and distinguishes from sibling removal tools by specifying 'volume'. Also adds unique context like 'Destructive; requires confirmation token'.

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?

No explicit guidance on when to use this tool vs alternatives (e.g., delete_volume_backup). No prerequisites or when-not-to-use mentioned.

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