ncloud_list_nas_volumes

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

The readOnlyHint annotation already signals a safe read operation. The description adds the 'current region' scoping constraint, which is useful. However, it does not disclose pagination behavior or return format, and the phrase 'all' is ambiguous given the pagination parameters in the schema.

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 a single, concise sentence that delivers the essential purpose without fluff. It is front-loaded with the action and resource, making it quickly scannable.

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 list tool with no output schema, the description gives the core purpose but omits details about pagination, default region behavior, or response structure. The pagination params suggest possible pagination, but the description says 'all,' leaving ambiguity. The presence of related sibling tools and no output schema make this minimally adequate but not 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%, with each parameter (pageNo, pageSize, zoneCode, regionCode, etc.) having a clear description. The tool description adds no additional parameter semantics, but the schema already provides adequate information, so the baseline 3 applies.

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 uses a specific verb ('List') and resource ('NAS volume instances') with a clear scope ('in the current region'). It unambiguously distinguishes this tool from siblings like ncloud_get_nas_volume_detail (singular detail) and ncloud_list_nas_snapshots (different resource type).

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 implies this tool is for listing NAS volumes but does not explicitly contrast it with alternatives or state when to prefer it over ncloud_get_nas_volume_detail or other listing tools. It provides clear context (current region) but no exclusions or alternative guidance.

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