ncloud_list_block_storage

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

The description adds that the tool operates within the 'current region', which is useful context. However, it does not describe behavior like pagination (despite having pageNo/pageSize parameters) or return format. The annotation readOnlyHint already indicates safety, so the description carries a lighter burden but still misses behavioral details.

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 sentence, concise and front-loaded. It efficiently conveys the core purpose without extraneous words. Slightly more detail could be added without losing conciseness, but it is already well-structured.

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?

Given the tool is a list operation with optional pagination parameters and no output schema, the description is minimally adequate. It explains the scope (in the current region) but does not mention pagination behavior, result structure, or that parameters filter results. For a list tool, this is somewhat incomplete.

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?

The schema already describes all 4 parameters with 100% coverage, so the description does not need to add parameter meaning. Baseline is 3 as per guidelines. The description does not provide extra examples or explanations 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 lists all block storage instances in the current region. The verb 'List' matches the tool name, and the scope is explicitly defined. Among sibling tools, it is distinct from other list tools like 'list_servers' or 'list_snapshots', making its purpose unambiguous.

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 no guidance on when to use this tool versus alternatives, such as 'get_block_storage_detail' for a single instance or other list operations. There are no hints about prerequisites, regional context, or when not to use it.

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