import_zonefile

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is covered; the description still adds real value by specifying exactly what gets destroyed (records absent from the file, not the whole zone object) and by noting the return is an Action. It stops short of stating permission/auth requirements or whether the replacement is atomic.

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?

Three short sentences, each front-loaded with the most consequential information (what it does, then the destruction warning and backup route, then the return type). No filler, no restatement of the tool name, and the destructive warning precedes rather than trails the usage advice.

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?

With no output schema, the mention of returning an Action fills an otherwise empty gap, and the destructive scope plus backup alternative cover the main risk for a two-parameter mutation. The remaining omission is the zonefile parameter's representation, which neither schema nor description pins down.

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 coverage is 50%: the zone parameter is documented in-schema as an ID or name with an example, while zonefile has no schema description. The description only adds that the file must be a BIND zone file, giving scope hints for both params but no detail on whether zonefile is raw text, an escaped string, or a path — leaving the undocumented parameter partly ambiguous.

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?

"Replace ALL records of a primary zone with a BIND zone file" names a specific verb (replace), the exact resource (all records of a primary zone), and the input format (BIND zone file). The uppercase "ALL" and the "primary zone" qualifier make the blast radius and eligible zone type unambiguous, distinguishing it from a record-level updater or the export counterpart.

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 gives a concrete operational directive — run export_zonefile first as a backup — which implicitly routes the agent to the sibling before invoking this one. What it lacks is an explicit statement of when this tool is the right choice versus per-record operations like add_rrset_records, and it doesn't say what happens on a zone that is not primary.

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