hcloud_show_load_balancer_topology

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

No annotations are given, so the description must disclose behavioral traits. It only says 'Show', indicating a read operation, but lacks details on pagination, depth, or limitations. This is minimal disclosure for a tool with no annotations.

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 a single, front-loaded sentence that conveys the core functionality without any redundant words. Every word adds value.

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, the description hints at the return structure (tree with listeners, pools, members), which is helpful. It is fairly complete for a show tool, though more detail on the output format could be beneficial.

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?

Both parameters have schema descriptions that are self-explanatory (region and loadbalancer_id). The description adds no additional meaning beyond the schema, so baseline 3 is appropriate.

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 clearly states the tool shows a 'load balancer topology tree' with specific components (listeners, pools, members). This distinguishes it from sibling tools like hcloud_show_load_balancer, which likely shows a different view.

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 explicit when-to-use or alternatives are provided. The description implies it is for retrieving a hierarchical view, but does not specify when to use this versus other show tools or list tools.

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