get_loadbalancer

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the operation is read-only, idempotent, or has any side effects. While 'Get' implies read-only, the description does not explicitly confirm this or mention any other behavioral aspects.

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, concise sentence that is front-loaded and efficient. However, it is very brief and could include more useful information without becoming verbose.

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 complexity of the API and the many sibling tools, the description lacks context. It does not explain what 'details' means, differentiate from similar tools like 'get_application_loadbalancer', or mention any output structure. The absence of an output schema increases the need for descriptive context, which is missing.

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 parameter schema has 100% description coverage, so the schema already defines each parameter (datacenter_id, loadbalancer_id, depth). The tool description adds no additional meaning beyond what the schema provides, fitting the baseline score of 3.

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 specifies the action 'Get details' and the resource 'specific load balancer', which clearly indicates a retrieval operation for an individual load balancer. The name differentiates it from sibling tools like 'get_application_loadbalancer', but the description itself does not explicitly distinguish between load balancer types.

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 (e.g., 'list_loadbalancers' or 'get_application_loadbalancer'). There is no mention of prerequisites, context, or exclusions.

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