ncloud_change_block_storage_size

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

Annotations already mark idempotentHint=true and destructiveHint=false. The description adds context that only size increase is supported, and the attached-volume/stopped-server requirement. This covers the main behavioral traits beyond annotations, though no return format or auth info is mentioned.

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, information-dense sentences. Every sentence adds critical value: what the tool does, when to use an alternative, and a necessary precondition. No filler or repetition.

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 resize operation with clear annotations and full schema coverage, this description is complete. It covers the operation type, scope constraint, platform distinction, and a critical prerequisite. No output schema exists, so return values are not expected to be documented.

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 the schema fully documents all three parameters. The description adds no additional parameter meaning beyond what is in the schema; it reinforces the 'increase only' constraint which the schema already captures.

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 opens with 'Resize a block storage volume (increase capacity only)', which is a specific verb+resource with a critical constraint. It also explicitly distinguishes itself from sibling tool ncloud_change_block_storage, clarifying the Gen2 vs KVM split.

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 explicit when-to-use guidance: 'Dedicated volume-size endpoint for Gen2 (XEN) storage. KVM-based block storage is NOT supported here — use ncloud_change_block_storage for KVM.' It also states a key prerequisite: server must be stopped if volume is attached.

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