ncloud_cdss_get_load_balancers

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

Annotations already declare readOnlyHint: true, and the description is consistent. The description adds context that the returned load balancers are scoped to the CDSS broker node public endpoint, but it does not disclose additional behaviors like return format or filtering criteria. Given the annotation coverage, this is an adequate but unexceptional level of transparency.

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 no extraneous words. It states the action and resource immediately.

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 read-only list operation with one parameter and a readOnlyHint annotation, the description is sufficient. It clearly explains the purpose and scope. Though the output schema is absent, the tool is simple enough that the description covers the essential context without needing to detail return values.

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 fully documents the sole parameter, serviceGroupInstanceNo, with the description 'Cluster instance number.' The tool description adds no additional parameter-specific insight, so the baseline score of 3 applies due to the high schema coverage.

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 the specific verb 'Get' with a clear resource ('load balancers') and context ('for CDSS broker node public endpoint'), cleanly distinguishing this tool from the generic ncloud_list_load_balancers sibling.

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 phrase 'for CDSS broker node public endpoint' provides clear contextual usage guidance, showing when this tool is relevant. However, it does not explicitly mention alternatives or exclusions, so it falls short of a 5.

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