hcloud_list_load_balancers

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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is covered. The description adds only the mild scoping note that results are limited to resources "you have available"; it says nothing about pagination, auto-pagination defaults, or the soft-cap, which are meaningful behaviors for a paged list endpoint.

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?

Two short sentences, front-loaded with the action, with no filler. It is efficient but borders on under-specification given the tool's filtering and pagination surface.

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?

There is no output schema, and the description does not describe the shape of the returned load balancer objects or pagination metadata. Combined with a six-parameter filtered list endpoint, the description is minimally adequate but leaves notable gaps for an agent relying on it alone.

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%, so all six parameters (name, page, sort, per_page, auto_paginate, label_selector) are already documented in the schema. The description adds no additional meaning about filtering or sorting semantics, so 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 states a specific verb and resource ("List Load Balancers", "Gets all existing Load Balancers"), which is unambiguous on its own. However, it offers no differentiation from closely related siblings such as hcloud_get_load_balancer, hcloud_list_load_balancer_types, or hcloud_list_load_balancer_actions, so the agent must infer the distinction.

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 list tool versus the sibling get/list tools, and no mention of prerequisites, pagination behavior, or filtering expectations. The reader is left to infer usage purely from the name.

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