ncloud_change_block_storage

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

Annotations (idempotentHint=true, destructiveHint=false) are supplemented with useful behavioral context: generation support and the prerequisite that attached storage must have the server stopped to resize. No contradiction with annotations, but no mention of reversibility or failure modes.

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?

Three concise sentences: purpose first, then platform support, then a critical prerequisite. No redundant wording; every sentence adds value.

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?

With full schema coverage and annotations, the description adds platform support and a key prerequisite. It lacks explicit guidance on when to choose this over ncloud_change_block_storage_size, and does not describe return values (though no output schema exists), but overall it is sufficiently complete.

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?

Input schema has 100% coverage with detailed parameter descriptions (e.g., blockStorageSize range, increment, and minimum). The description's 'resize volume and/or update name/description' maps to parameters but adds no additional parameter-level semantics beyond the schema.

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 specific verb and resource: 'Change block storage instance' with parenthetical details 'resize volume and/or update name/description'. This distinguishes it from siblings like ncloud_change_block_storage_size and ncloud_set_block_storage_protection.

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 clear operational context: supports Gen2 (XEN) and Gen3 (KVM), and requires server to be stopped for attached storage resize. However, it does not explicitly mention alternatives or exclusions, such as using ncloud_change_block_storage_size for size-only changes.

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