ncloud_delete_block_storage

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

Annotations already declare destructiveHint=true and idempotentHint=true, which convey the core behavioral trait. The description adds 'Permanently delete' and a warning, reinforcing the destruction but not adding significant new behavior beyond annotations. No contradiction with annotations.

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 extremely concise (one sentence after a prefix), with the warning front-loaded and the critical execution condition stated immediately. Every word adds value; no redundancy or fluff.

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 delete operation with no output schema, the description adequately covers the action, safety requirement, and resource. It does not specify return values, but that is acceptable given the tool's simplicity. Minor gap: no mention of error handling or what happens when deletion fails.

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%, with both parameters described in the schema. The description does not add additional parameter guidance beyond what the schema provides (e.g., 'confirm' default, 'blockStorageInstanceNoList' as array of strings). Baseline 3 is appropriate.

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 verb ('delete'), resource ('block storage instances'), and scope ('one or more'). It explicitly warns of permanence and uses a safety gate ('confirm=true'), distinguishing it from sibling tools like 'ncloud_create_block_storage' or 'ncloud_attach_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 explicitly instructs the agent to set 'confirm=true' to execute, which is a clear usage guideline. While it doesn't provide explicit when-not-to-use or alternative tool names, the warning and safety requirement are sufficient for most scenarios. Sibling tools are numerous but contextually different.

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