hcloud_zone_rrset_remove_records_action

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. The description adds genuinely non-obvious behavior: the RRSet is auto-deleted when it becomes empty, and the primary-mode restriction with its specific error code. It doesn't say what happens when a listed record doesn't exist, which is the main residual 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?

Front-loaded with the action, then the auto-delete side effect, then the applicability constraint and error table — a sensible priority order. The repeated markdown anchor links add mild noise, but nothing meaningful is wasted.

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 5-parameter nested-body mutation with no output schema, the description covers the critical side effect, the mode restriction, and the operation-specific error. It could say more about the returned action object or the matching semantics (value is used to identify a record), but the essentials are 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 80%, with rr_name formatting rules, the rr_type enum, and the records body constraints all documented in the schema. The description adds no parameter-level guidance of its own, so baseline 3 applies.

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 opens with a specific verb+resource ("Remove Records from an RRSet") and scopes it to records within an existing RRSet in a Zone. This clearly distinguishes it from sibling mutations like hcloud_zone_rrset_add_records_action, set_records_action, and update_records_action.

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 states the key precondition explicitly — "Only applicable for Zones in primary mode" — and backs it with the 422 incorrect_zone_mode error. It stops short of naming which sibling to use instead when the intent is replacement versus removal, leaving that inference to the agent.

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