cloud_get_load_balancer

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits. It fails to mention any side effects, required permissions, rate limits, or error conditions. The tool is expected to be read-only, but this is not stated, and no other behavioral details are given.

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 with no redundant words. It is front-loaded with the core purpose. However, its brevity sacrifices necessary detail for a complete understanding, placing it slightly below a perfect score due to omission of critical information.

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 that the tool has an output schema, the description does not need to detail return values, but it should still cover prerequisites, usage context, and potential errors. The description lacks any indication of error handling, required permissions, or how to obtain the ID, making it incomplete for an agent to reliably invoke.

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 0% description coverage for the parameter 'load_balancer_id', and the description only says 'by ID', which adds minimal context. It does not explain the format, source, or validation of the ID. The description should provide more guidance on how to obtain or format the identifier.

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 a single load balancer by ID.' clearly states the action (get) and the resource (load balancer), and implies a unique identifier. It distinguishes itself from sibling tools like 'cloud_list_load_balancers' (which retrieves all) and 'cloud_create_load_balancer' (which creates), making the purpose unambiguous.

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?

No explicit guidance is provided on when to use this tool versus alternatives. It does not mention that this tool is appropriate when a specific ID is known, versus using the list tool for discovery, or when to avoid using it (e.g., if the ID doesn't exist). The description lacks context for decision-making.

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