dns_import_zone_file

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

With no annotations provided, the description carries full burden. It discloses the destructive nature ('replaces all records') but omits other behavioral traits such as whether the operation is atomic, requires the zone to exist, or handles validation errors. Output schema exists but its contents are unknown.

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?

A single sentence front-loads the verb and resource, with the critical side effect in parentheses. Every word earns its place; no redundancy.

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?

While the description captures the core purpose and side effect, it lacks completeness for a tool that replaces all records. Prerequisites (zone must exist), relation to dns_validate_zone_file, and handling of partial imports are not addressed. Adequate but with clear gaps.

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 0%, so the description must compensate. It only implies that 'zone_id' identifies the zone and 'zone_file' contains the BIND file content. No details on format, length, or constraints are provided, leaving the agent to guess.

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 verb 'import', the resource 'records into an existing zone', the source 'BIND zone file', and the critical side effect 'replaces all records'. This distinguishes it from siblings like dns_create_record (adds individual records) and dns_export_zone_file (exports).

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 implies when to use (importing a full zone file overwriting all records) but does not explicitly exclude alternatives or mention prerequisites like zone existence or file validation. Siblings like dns_validate_zone_file exist, but no guidance on pre-validation is given.

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