ncloud_list_block_storage

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

The annotation readOnlyHint=true already signals that the tool performs a read-only operation, so the description's 'List' is consistent. The description adds the important 'current region' scoping constraint, but does not disclose pagination behavior, response format, or whether filters change the 'all' semantics. With annotations covering safety, this is adequate but not rich.

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, front-loaded sentence with zero wasted words. Every term ('List', 'block storage instances', 'current region') is meaningful and directly conveys the tool's function.

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?

While the description is clear and the schema/annotations handle parameters and safety, the description is minimal. It does not mention that the tool supports filtering (despite saying 'List all') nor describe the return structure or pagination behavior. For a list tool without an output schema, this could leave the agent uncertain about what fields are returned. The description is adequate but has clear gaps.

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?

All four parameters in the schema have descriptions covering pagination pageNo/pageSize and filtering by serverInstanceNo/blockStorageInstanceNoList. The tool description adds no additional parameter semantics beyond what the schema already provides. According to the rubric, this is baseline 3 because schema coverage is 100%.

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 'List all block storage instances in the current region' uses a specific verb ('List') and resource ('block storage instances'), with clear scope ('current region'). It clearly distinguishes from sibling tools like ncloud_get_block_storage_detail (get a single instance) and ncloud_create_block_storage (create).

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 clearly indicates the tool's use case: listing block storage instances. It does not explicitly mention exclusions or name alternative tools (e.g., 'for a single instance, use get_block_storage_detail'), but the context is straightforward and implies when to use this list operation. No misleading guidance is present.

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