hcloud_get_load_balancer_action

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

Annotations already cover the safety profile (readOnlyHint=true, destructiveHint=false, openWorldHint=true), so the description is not obligated to restate that. It does add a genuinely useful behavioral fact beyond structured data: the endpoint is deprecated as of the linked changelog date, which affects whether an agent should pick it at all. It omits any note about the polling behavior implied by the 'wait' parameter, keeping it short of a 5.

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?

Front-loads the deprecation notice and then gives one sentence of purpose — no wasted text. The markdown heading plus repeated restatement of the purpose is slightly redundant but not harmful.

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 say what an Action object contains or how a caller should read the result, nor does it give a migration path despite the deprecation. For a simple two-ID lookup tool this is adequate but leaves gaps an agent would have to guess at.

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 three parameters (id, action_id, wait) are already documented in the schema, including the polling semantics of 'wait'. The description adds no parameter-level detail, so the 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?

States a specific verb and resource ('Get an Action for a Load Balancer'), and the load-balancer scoping distinguishes it from the generic hcloud_get_action and the server/volume/network action getters. It does not explicitly name those siblings, but the resource qualifier is enough to route an agent.

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?

It flags that the operation is deprecated and links a changelog, which implies 'prefer something else,' but it never says what to use instead (e.g., hcloud_get_action or hcloud_list_load_balancer_actions) or under what conditions this tool is still correct. The usage signal is implied rather than stated.

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