hcloud_delete_zone

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered structurally. The description adds nothing beyond that: it never states that the deletion destroys all records in the zone, whether it is reversible, or how the `wait` polling parameter affects the call's behavior.

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 is a pure restatement of the first with a link, so not every sentence earns its place. The size is fine; the redundancy is the flaw.

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, open-world mutation with no output schema, the description should warn that all rrsets inside the zone are removed and note any protection/irreversibility concerns. It supplies none of that, leaving the agent dependent entirely on the destructiveHint annotation.

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 both `id_or_name` and `wait` are already documented structurally. The description adds no extra meaning (e.g. accepted name formats, or what happens when `wait` is false), making the baseline 3 appropriate.

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 first sentence names a specific verb and resource ("Delete a Zone"), which is clearly distinguishable from siblings like hcloud_delete_zone_rrset or hcloud_update_zone. The second sentence only restates the same fact with a doc link, so no additional differentiation is offered.

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 alternatives (e.g. hcloud_delete_zone_rrset for individual records) and no prerequisites, such as whether zone protection blocks deletion. 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.