iaas_get_load_balancer

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is fully covered by structured data. The description adds nothing extra: no note on what happens if the id does not exist, no error behavior, no pagination or scoping context. It only repeats the verb already in the name.

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?

It is short, but not efficient: the first two sentences say the same thing ('Get load balancer' / 'Get load balancer with a given id') and the third sentence duplicates the endpoint already carried in the annotation title. Front-loading is fine, but the content is redundant rather than informative.

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?

This is a simple read tool whose safety semantics are fully in annotations and whose parameters are fully in the schema, so little is required. Still, the description offers no distinguishing context from the many sibling load balancer tools (create, delete, scale, network interface, list), leaving selection ambiguous for a complex tool surface.

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%, with both id and apiVersion documented in the schema, so the baseline is 3. The description's phrase 'with a given id' merely confirms the required path parameter and adds no format, source, or discovery guidance (e.g. where to obtain a load balancer id).

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 says 'Get load balancer with a given id', which identifies a retrieve-single-resource operation, but it is essentially a restatement of the tool name plus the HTTP route. It never explicitly distinguishes itself from the sibling iaas_get_load_balancers or from iaas_get_load_balancer_network_interface; an agent must infer the plural/singular split from the names alone.

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?

There is no guidance on when to use this versus iaas_get_load_balancers (list) or iaas_get_load_balancer_network_interface. The only hint, 'with a given id', is already implied by the required id parameter in the schema.

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