ncloud_change_nas_volume_size

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

Annotations already provide idempotentHint=true and destructiveHint=false, indicating a safe, repeatable operation. The description adds no additional behavioral context, such as whether the volume must be unmounted or if there is downtime.

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?

Extremely concise at one sentence, front-loading the verb and resource. However, it may be too terse; a bit more detail (e.g., 'Resizes a NAS volume to a new capacity') would improve without adding bloat.

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?

Lacks completeness: no mention of return values (no output schema), expected side effects, or how to verify the change. For a mutation tool, more contextual information is needed for an agent to invoke it correctly.

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 clear descriptions for both parameters (volumeSize range and increments, nasVolumeInstanceNo as identifier). The tool description does not add any meaning beyond the schema, so a baseline score of 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 'Change the size of a NAS volume instance' clearly indicates the action (change) and resource (NAS volume). It effectively distinguishes from sibling tools like create, delete, or snapshot operations, though it could be more specific (e.g., 'resize').

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?

No guidance on when or when not to use this tool relative to alternatives. For example, it doesn't mention prerequisites (e.g., volume must be in certain state) or that this is the only way to resize a NAS volume.

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