ncloud_attach_block_storage

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

Annotations already declare idempotentHint=true and destructiveHint=false. The description adds the important behavioral detail that the tool automatically polls until the block storage status is 'CREAT' before attaching, which goes beyond annotations and helps the agent understand wait behavior.

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 two sentences, each serving a distinct purpose: stating the core action and highlighting the auto-wait behavior. No redundancy, fully front-loaded, and every word earns its place.

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 simple attach operation with annotations and clear schema, the description covers the essential behavior. It could optionally mention the return value or prerequisites, but given the low complexity, it is sufficiently complete. No missing critical context.

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% and both parameters (serverInstanceNo, blockStorageInstanceNo) are described with clear names and descriptions in the schema. The description does not add additional semantic information about the parameters beyond what the schema provides, so 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 action ('Attach a block storage instance to a server') and distinguishes it from sibling tools like detach_block_storage or change_block_storage. The additional note about auto-waiting adds specificity.

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 mentions the auto-wait behavior for pending block storage creation, but does not provide explicit guidance on when to use this tool versus alternatives (e.g., detach), nor does it state prerequisites or conditions (e.g., server must exist, block storage must be in appropriate state). Usage is implied but not explicitly spelled out.

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