ncloud_cdss_get_load_balancers

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

Annotations already declare readOnlyHint=true, indicating a safe read operation. The description states 'Get', which aligns with readOnlyHint. No additional behavioral traits (e.g., rate limits, auth requirements, side effects) are disclosed. With annotations covering the safety profile, the description adds minimal extra 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, clear sentence with no fluff. All words are necessary to convey the tool's purpose. It is appropriately front-loaded and concise.

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's simplicity (1 required parameter, read-only, no output schema) and rich annotations, the description is adequate but not complete. It does not describe the return format (e.g., list of load balancer IDs/names), which an agent might need to process the result. While the purpose is clear, the lack of return information leaves a gap.

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 one required parameter ('serviceGroupInstanceNo' with description 'Cluster instance number'), and schema description coverage is 100%. The tool description does not add any further meaning or context about the parameter beyond what the schema already provides. Per rubric, baseline 3 is appropriate when schema coverage is high.

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 'Get available load balancers for CDSS broker node public endpoint' is specific: it clearly identifies the verb (Get), the resource (load balancers), and the context (CDSS broker node public endpoint). This differentiates it from sibling tools like ncloud_cdss_get_cluster_detail or ncloud_cdss_get_broker_info.

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. It does not mention prerequisites, exclusions, or conditions under which this tool should be chosen over other CDSS 'get' tools. The agent must infer usage from the purpose alone.

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