hcloud_update_zone_rrset

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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is covered. The description adds genuine behavioral context with the primary-mode restriction and the specific error code, but it never says what the update destroys or whether unmentioned fields are preserved, which matters for a destructive mutation.

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 core purpose is front-loaded and the mode restriction plus error table are compact and skimmable. The markdown anchor links (#tag/zone-rrsets, #tag/zones) are noise that adds length without meaning.

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 4-param mutation whose annotations carry the destructive/read-write profile, the description supplies the one non-obvious constraint (primary mode) plus its failure signal. It stops short of explaining replace-vs-merge semantics for the RRSet, but the schema partially covers the labels overwrite behavior.

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 75% and the schema already documents rr_name formatting, rr_type enum values, and the labels-overwrite semantics. The description adds nothing about any of the four parameters, so it neither compensates for the remaining gap nor repeats what is better handled in the schema.

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 clear verb+resource: 'Update an RRSet in the Zone'. It is unambiguous what the tool mutates, but it does not distinguish itself from the many sibling record-level operations (hcloud_zone_rrset_update_records_action, hcloud_zone_rrset_set_records_action, add/remove_records), so an agent cannot tell from the text which of these mutates the RRSet itself versus its records.

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 gives one real precondition, 'Only applicable for Zones in primary mode', tied to a concrete 422 incorrect_zone_mode error. It offers no guidance on when to choose this over the record-level siblings, which is exactly the ambiguity an agent will face here.

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