ncloud_create_block_storage

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

Annotations only have destructiveHint: false. The description adds behavioral details: required zone, volume type, size; hypervisor-specific attachment behavior; and the dryRun option. It does not describe idempotency or error cases, but the information provided is sufficient given the minimal 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?

Three sentences: first states purpose and required params, second and third add hypervisor-specific details and dryRun. Front-loaded, concise, and no unnecessary information.

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 9 parameters and no output schema, the description covers the main workflow and explains key parameter interactions (zoneCode vs serverInstanceNo). It lacks return value explanation (no output schema) and error handling, but for a creation tool, it is fairly 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?

Schema description coverage is 100%, so baseline is 3. The description adds extra context about hypervisor-specific usage (zoneCode required when no serverInstanceNo, serverInstanceNo only for XEN) and the dryRun option, providing added value 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 tool creates a new block storage instance, lists required parameters (zoneCode, blockStorageVolumeTypeCode, blockStorageSize), and distinguishes behavior between XEN and KVM hypervisors, which differentiates it from sibling tools like 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 provides explicit guidance on when to use dryRun=true for preview and when to attach storage (at creation for XEN, after via ncloud_attach_block_storage for KVM). It mentions required parameters but does not explicitly state when not to use this tool, though the sibling context provides alternatives.

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