hcloud_list_load_balancers

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

With no annotations, the description bears full responsibility for behavioral transparency. It only states the basic action, omitting important traits like pagination behavior (e.g., whether limit caps results or enables cursor), ordering, or that listing is regional (implied by required region parameter but not explained).

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 very short (one sentence), which is concise but lacks crucial details. It could be restructured to include brief information about region and limit without losing conciseness.

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 no output schema and the tool being a list operation with two parameters, the description is incomplete. It does not explain what the output contains, pagination behavior, or how the region parameter affects results (e.g., is it required for all clouds?). More detail is needed for a complete context.

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 coverage is 100% with simple descriptions ('Region', 'Max results'). The description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the description does not worsen understanding but also provides no extra value.

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 'List ELB load balancers' clearly states the action (list) and resource (ELB load balancers), distinguishing it from other list tools for different resources. However, using 'ELB' may be slightly ambiguous without context, and it could be more specific like 'list all load balancers in a region'.

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 guidance is provided on when to use this tool versus alternatives, such as 'hcloud_show_load_balancer' for a single load balancer. There is no mention of prerequisites, limitations, or preferred use cases.

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