iaas_delete_block_device

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

Annotations already declare destructive/readOnly/idempotent hints, but the description adds substantive behavior beyond them—namely the attachment guard and the persistent=true requiring purge=true rule. These are non-obvious conditions an agent would otherwise miss.

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 numbered rules are clear and useful, but the phrase 'Delete a BlockDevice' is repeated verbatim at the start, which is wasted space. Structure is scannable but front-loading suffers from the duplication.

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 destructive single-resource delete with no output schema, the description covers the key operational caveats (attachment state, persistent/purge rules) while annotations carry the safety profile. Nearly complete, though it doesn't clarify the purge vs forceDelete distinction.

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 100% schema coverage the baseline is 3, but the description adds meaning beyond the schema: it explains that 'purge' must be set true specifically for persistent block devices. Note a slight semantic drift—the schema frames purge/forceDelete as force-delete, while the description ties purge to deleting persistent devices.

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?

States a specific verb+resource ('Delete a BlockDevice'), so an agent knows exactly what it does and can distinguish it from iaas_get_block_device or iaas_create_block_device by name. It doesn't explicitly call out sibling alternatives, but the delete intent is unambiguous.

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?

Provides real preconditions: it cannot be deleted while attached to a machine, and the persistent/purge interaction determines whether deletion succeeds. This is clear operational context, though it does not name alternative tools or explicitly state when to prefer them.

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