hcloud_load_balancer_change_protection_action

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. The description adds nothing beyond that: it does not explain that this only toggles delete protection, whether changes are reversible, or that the call returns a pollable action.

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 short and front-loaded, but the first sentence duplicates the title and the second sentence paraphrases it. Almost no information is added per sentence.

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 mutation with a nested body and no output schema, the description should clarify what is being protected, that the result is an async action, and how wait interacts with it. None of that is present.

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 only 67%, and the description contributes no parameter meaning at all. With partial coverage and no compensating text, the agent must rely entirely on the schema for id, body.delete, and 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 description states a verb and resource ('changes the protection configuration of a Load Balancer'), but it largely restates the tool name and title. It does not say which protection (delete protection only) or distinguish itself from hcloud_update_load_balancer or the many sibling change_protection tools for other resources.

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 when-to-use or when-not-to-use guidance is given. There is no mention of alternatives such as hcloud_update_load_balancer or the parallel change_protection tools for servers, volumes, and networks.

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