hcloud_zone_change_protection_action

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

Annotations already declare readOnlyHint=false, destructiveHint=true and openWorldHint=true, so the safety profile is known. The description adds nothing on top: it does not explain that setting 'delete=true' protects the Zone from deletion while 'false' makes it deletable, does not mention that this is asynchronous and polled via the 'wait' flag, and gives no reversibility or permission context. For a destructive mutation this is a real gap.

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, but the second sentence merely restates the heading ('Change a Zone's Protection' / 'Changes the protection configuration of a Zone'), so the tiny body contains no information beyond the title. Conciseness here is achieved by omission rather than by density.

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?

This is a destructive, open-world mutation with a nested body object and no output schema. The description does not cover what the protection setting means, what changes as a result, the async action/polling behavior implied by 'wait', or required permissions — the bare minimum for an agent to call it safely is missing.

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 coverage is 67% and the description contributes zero parameter meaning — it never mentions id_or_name, wait, or the delete flag. The critical ambiguity is the polarity of 'delete' (protection enabled vs. deletion allowed), which the schema phrase 'Prevents the Zone from being deleted' only partially resolves; the description should disambiguate it and does not.

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 names a verb ('Changes') and resource ('protection configuration of a Zone'), so the general purpose is inferable. But 'protection' is never defined — it does not say whether this toggles delete protection on or off — and there is no differentiation from sibling protection tools such as hcloud_zone_rrset_change_protection_action or hcloud_server_change_protection_action beyond the resource word.

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 statement of when to use this tool, when not to (e.g., prefer hcloud_update_zone for other Zone settings), or what prerequisites/permissions are required. The agent must infer everything from the tool name.

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