ncloud_list_lb_rules

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

The readOnlyHint annotation already declares this as a safe read operation. The description adds the scope 'registered to a load balancer listener' but does not disclose additional behavioral details such as pagination, ordering, or return format. Given the annotation coverage, this is adequate but not enriched.

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, short, front-loaded sentence with no filler. Every word earns its place, and it immediately communicates the tool's purpose.

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?

This is a low-complexity list tool with one parameter and a read-only annotation. The description, combined with the schema and annotation, provides sufficient information for an agent to select and invoke the tool. The absence of an output schema or details about rule structure is acceptable given the simplicity, though a note about return content would push it to 5.

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%: the only parameter, loadBalancerListenerNo, is described as 'Load balancer listener number' in the schema. The tool description adds no additional parameter meaning, such as format, validation, or source of the value. Since the schema fully documents the parameter, the baseline of 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 ('rules registered to a load balancer listener'), clearly distinguishing this from siblings like ncloud_list_lb_listeners and ncloud_list_load_balancers. It precisely states the tool's function without ambiguity.

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 clear usage context: use this when you need to retrieve rules for a specific load balancer listener. It does not explicitly name alternatives or exclusions, but the resource scoping ('registered to a load balancer listener') makes it obvious when to select this tool over others.

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