ncloud_delete_block_storage

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

The description explicitly warns 'Destructive' and notes 'Permanently delete', adding meaningful context about irreversibility. It also explains the confirm=true requirement, which goes beyond the annotations' destructiveHint and idempotentHint by detailing the safety gating mechanism.

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 focused sentence with a leading warning emoji, immediately conveying destructive impact, followed by the critical confirmation requirement. No filler or redundancy.

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 two-parameter destructive operation with annotations covering idempotency and destructiveness, the description sufficiently covers purpose, the confirmation guard, and the scope (one or more instances). It omits prerequisites like detaching the volume first, but this is not critical given the simple schema and existing annotations.

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 description coverage is 100%, so both parameters are already fully described. The description's mention of 'Set confirm=true' adds no new semantic value beyond the schema's own wording ('Must be true to actually execute'), yielding a baseline score.

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 states a specific verb+resource: 'Permanently delete one or more block storage instances.' This clearly distinguishes it from sibling delete operations (e.g., delete_snapshots, delete_nas_volumes) by naming the exact resource type and scope (block storage).

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 gives no guidance on when to use this tool versus alternatives, such as delete_snapshots or detach_block_storage. It implies usage only via the provided operation name and general delete semantics, with no exclusions or contextual hints.

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