ncloud_list_load_balancers

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

Annotations already provide readOnlyHint: true, so the description adds only 'in the current region' beyond that. No mention of pagination behavior or other traits (e.g., rate limits, data refresh). The description is consistent with annotations, so no contradiction.

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?

Single sentence, no redundant words. Front-loaded with action and resource. Every word earns its place.

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, it omits what the response contains (no output schema) and does not explain how filtering parameters interact. For a list tool with 6 optional filters, more context on parameter usage or result format would improve completeness.

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 input schema has 100% coverage with descriptions for all 6 parameters (vpcNo, pageNo, pageSize, etc.). The description does not add any additional meaning or context beyond what the schema already provides, so baseline score 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?

Description clearly states the action 'List' and the resource 'load balancer instances', with a scope qualifier 'in the current region'. It distinguishes from sibling tools like ncloud_get_load_balancer_detail (single instance) and ncloud_create_load_balancer (write operation).

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 explicit when-to-use or when-not-to guidance is provided. The description implies listing all instances but does not mention that it is read-only or suggest alternatives like using filtering parameters. However, the purpose is straightforward for a list tool.

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