hcloud_zone_change_primary_nameservers_action

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

The description adds useful context beyond the annotations by saying it overwrites primary nameservers and only applies in secondary mode. The annotations already mark it destructive and open-world, and the description reinforces the destructive nature without contradicting them. It does not explain the effect on DNS propagation or AXFR behavior, but annotations and schema cover the safety profile.

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 and short: it states the operation, clarifies overwrite semantics, gives the mode restriction, and lists the relevant error. Every sentence and table row earns its place.

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 zone action with rich nested schema and annotations, the description covers the key precondition and operation-specific failure mode. It does not explain return behavior or wait polling, but those are either schema-documented or not essential to invocation.

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 67%, with the nested primary_nameservers fields, id_or_name, and wait described in the schema. The description itself adds no parameter-level meaning, so the schema carries most of the burden and baseline 3 is 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 description states a specific verb and resource: changing primary nameservers for a Zone. It also clarifies the mutation is an overwrite and scopes it to Zones in secondary mode, distinguishing it from other zone actions.

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?

The description clearly states the key applicability condition: only Zones in secondary mode. It reinforces this with the 422 incorrect_zone_mode error, though it does not explicitly name alternative tools or actions for primary-mode zones.

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