ncloud_get_load_balancer_detail

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

Annotations provide readOnlyHint=true, so the agent knows this is a safe read operation. The description adds only 'detailed information,' which is generic and does not disclose response format, pagination, or any additional behavioral traits. No contradiction with annotations exists.

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 wasted words. It immediately states the purpose and resource.

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 one-parameter read-only tool, the description is adequate. However, since there is no output schema, it would be slightly more complete if it indicated what kind of 'detailed information' is returned (e.g., configuration, health, IPs). Still, the tool is understandable as-is.

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 loadBalancerInstanceNo parameter is described as 'Load balancer instance number to query.' The tool description adds no further parameter context, so it relies on the schema. Baseline 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 ('get'), identifies the resource ('load balancer instance'), and scopes it to 'a specific' instance. This clearly distinguishes it from sibling tools like ncloud_list_load_balancers, which lists instances.

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 word 'specific' implies this tool is for querying a single instance by number, contrasting with list operations, but there is no explicit guidance on when to use this versus alternatives like ncloud_list_load_balancers or ncloud_get_target_group_detail. Usage context is implied rather than stated.

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