Import DNS Zonefile

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

The description adds that the tool overwrites all existing RRSets, which provides some behavioral context beyond the destructiveHint annotation. However, it does not clarify whether other zone settings (e.g., TTL, nameservers) are affected, leaving some behavioral ambiguity.

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 are efficient and front-loaded: the first states the core action, the second adds a critical behavioral note. No extraneous text.

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 straightforward import operation, the description covers the essential action and effect. Annotations provide safety profile. Lacking return value explanation, but no output schema exists; overall adequate.

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?

Both parameters have descriptions in the input schema (100% coverage). The description adds no additional semantic information beyond what the schema already provides. 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 clearly states the tool replaces the contents of a DNS zone using a zonefile, explicitly mentioning it overwrites all existing RRSets. This distinguishes it from sibling tools like hetzner_export_zonefile or hetzner_create_zone.

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 explains what the tool does but provides no explicit guidance on when to use it versus alternatives, nor does it mention prerequisites or when not to use it. The context is clear but lacks usage direction.

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