hcloud_zone_rrset_set_records_action

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

Annotations already flag destructiveHint=true, but the description earns its keep by spelling out the overwrite semantics (the entire RR set is replaced, not merged) and the zone-mode restriction that triggers a specific error. It doesn't mention that the call produces an async action polled via the `wait` flag, but the destructive behavior itself is well disclosed.

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 front-loaded with the operation name and its overwrite semantics before any constraint or error detail. The error table is somewhat boilerplate for a single row, but each section carries actionable information.

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 DNS mutation with a nested records array, no output schema, and an async action model, several things are left unstated: that an empty set is rejected (so deletion requires remove_records), TTL handling, and partial-failure behavior. The primary-mode restriction and overwrite semantics cover the most important gaps, but not all.

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 80%, so the baseline would be 3, but "Overwrites" adds meaning the schema lacks: the `records` array replaces the existing set rather than appending to it. It also ties the `id_or_name`/`rr_name`/`rr_type` triple to the primary-mode constraint, which the schema doesn't express.

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 specific verb and resource ("Set Records of an RRSet") and immediately clarifies the semantics with "Overwrites the resource records (RRs) of an existing RRSet," which implicitly distinguishes it from the add/remove/update record siblings. It doesn't explicitly name those alternatives, so the differentiation requires the agent to infer it from "overwrites."

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?

"Only applicable for Zones in primary mode" is a genuine precondition, reinforced by the 422 incorrect_zone_mode error row. However, with three close siblings (add_records, remove_records, update_records) doing similar work, the description never says when to pick this full-replacement tool over them.

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