hcloud_load_balancer_remove_target_action

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

Annotations already declare destructiveHint=true and openWorldHint=true, but the description adds no operational context: it does not say that traffic immediately stops being routed to the removed target, whether in-flight connections are drained, or whether the action is asynchronous. For a destructive mutation, saying only "removes" leaves the blast radius undisclosed.

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?

It is short and front-loaded, with the action heading followed by a single sentence. The heading duplicates the tool name, so there is minor redundancy, but nothing is padded.

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 destructive, nested-object mutation with no output schema, the definition omits the essentials an agent needs beyond the schema: the effect of removal on traffic, whether it is reversible, and the fact that wait=true polls the resulting action. Annotations cover the safety hint but not the operational consequences.

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 the nested target objects are thoroughly documented in-schema, including enum meanings and IP restrictions, so the baseline is 3. The description contributes nothing beyond the schema for the three parameters (id, body, wait).

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 verb and resource are stated plainly ("Removes a target from a Load Balancer"), so the polarity is distinguishable from hcloud_load_balancer_add_target_action. However, the sentence is essentially the tool name expanded, with no indication of which target kinds (server, label_selector, ip) are involved or what effect the removal has.

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 versus add_target_action, no prerequisites (e.g. permissions, whether the target must currently exist), and no note that the operation can be reversed by re-adding. The agent must infer everything from the name.

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