hcloud_delete_load_balancer

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=true, so the safety profile is covered elsewhere. The description adds nothing beyond that: it does not say the deletion is irreversible, what happens to attached targets/services, whether deletion protection blocks it, or that an async action results (relevant given the 'wait' parameter).

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?

Extremely short, but the second sentence is a verbatim restatement of the first and of the tool name, so no sentence earns its place beyond the first line.

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 two-parameter tool with no output schema, the annotations and schema carry most of the burden, but the description leaves real gaps: irreversibility, the asynchronous action/polling semantics tied to 'wait', and any deletion-protection prerequisite are unstated.

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%, with 'id' and 'wait' fully documented in the schema, so the baseline of 3 applies. The description contributes no additional meaning about the id or the polling behavior of '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 text only restates the tool name twice: 'Delete a Load Balancer' followed by 'Deletes a Load Balancer.' There is no added scope, no mention of what a Load Balancer is here, and no differentiation from the many sibling delete_* tools beyond the name itself.

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 guidance on when to use this versus alternatives such as hcloud_update_load_balancer, detaching targets first, or whether deletion protection must be disabled. The agent must infer all preconditions on its own.

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