Set DNS Zone RRSet Records

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is known. The description earns credit by adding the specific destructive detail — exactly what gets removed (existing records not in the payload) — which explains the idempotent full-sync semantics. No contradiction with annotations.

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?

Two sentences with zero waste. The primary action is front-loaded, and the destructive consequence is stated immediately in the second sentence. Every word 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 4-parameter, all-required mutation with no output schema, the description captures the essential semantics: full replacement and destructive removal. Minor gaps exist — no mention of response behavior, prerequisites like zone existence, or how TTL/protection interact — but the schema and annotations carry the remaining burden adequately.

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 the schema already documents all four parameters, including 'records' as a 'Full replacement list'. The description reinforces this by stating the consequence of the records payload (removal of omitted entries), adding marginal meaning beyond the schema but not compensating for anything missing.

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 verb 'Replace' is specific, the resource is clearly identified ('the full list of records in an RRSet'), and the second sentence ('Existing records not in the payload are removed') sharply differentiates this from siblings like hetzner_add_zone_rrset_records and hetzner_remove_zone_rrset_records. An agent can distinguish this tool without inspecting other schemas.

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 'full list' and 'removed' phrasing implies this is for wholesale replacement rather than incremental changes, but the description never names alternatives or states when not to use it. Given siblings add_zone_rrset_records, remove_zone_rrset_records, and update_zone_rrset_records exist, explicit routing guidance would be valuable; the tool leaves it to inference.

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