hcloud_show_load_balancer

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

Annotations already declare readOnlyHint=true, idempotentHint=true and openWorldHint=true, so the safety profile is covered. The description adds nothing beyond that: no note on what the returned detail includes, whether the ID must come from a list call, or what happens if the region/ID pair is invalid.

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?

A single, front-loaded sentence with no filler or redundancy. It is efficient, though its brevity borders on under-specification rather than polished 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?

For a simple two-required-parameter read tool with full schema coverage and read-only annotations, the description is minimally sufficient to call it. It still leaves the agent guessing about return contents and the region parameter's constraint, which matters given there is no output schema.

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% and both parameters (region, loadbalancer_id) are documented in the schema, so the baseline is 3. The description contributes no extra meaning, such as ID format or whether region must match the load balancer's actual region.

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 ('Get details') and resource ('a specific load balancer'), which clearly separates it from hcloud_list_load_balancers. It does not, however, distinguish itself from hcloud_show_load_balancer_topology, the other show-style sibling for the same resource.

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?

Usage is only implied: the word 'specific' suggests the agent must already know a load balancer ID, so listing via hcloud_list_load_balancers is the natural prerequisite. No explicit when-to-use, when-not-to-use, or alternative (topology) is named.

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