hcloud_show_load_balancer_topology

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 the useful fact that the result is a topology tree spanning listeners, pools, and members, but says nothing about depth, shape, or whether all three levels are always populated.

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 the resource named first and the returned entities immediately after. No filler, no restatement of the tool name, nothing that could be cut.

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 two-parameter read-only tool with no output schema, the description is minimally sufficient: it names the returned entities, which is the main thing the schema cannot convey. However, it leaves the tree's structure and any per-level detail unexplained, so an agent cannot anticipate the response format.

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% for both required parameters (region, loadbalancer_id), so the schema carries the parameter burden. The description adds no meaning about region scoping or ID format beyond what the schema already states; 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 pairs a specific verb ("Show") with a specific resource ("load balancer topology tree") and enumerates the contained entities (listeners, pools, members). This distinguishes it from the flat siblings hcloud_list_listeners, hcloud_list_pools, and hcloud_list_members by signalling an aggregated hierarchical view, though it never explicitly contrasts with hcloud_show_load_balancer.

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 statement of when to choose this tool over hcloud_show_load_balancer or the three separate list_* calls for listeners, pools, and members. The parenthetical contents hint at an aggregation convenience, but the agent must infer that; no prerequisites, exclusions, or alternatives are named.

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