export_dns_zone

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does disclose the output shape (JSON array), the full-scope behavior ('all DNS records'), and the prerequisite workflow, and the verb 'export' strongly implies a non-destructive read. It does not explicitly state read-only/no side effects, nor how large zones or pagination are handled, which is a meaningful gap for a tool intended for backups.

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 earning its place: the first delivers the core purpose, the second the use case, and the third the prerequisite workflow. The most important scoping information is front-loaded, and nothing is repeated from the schema.

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 tool with a single optional parameter and no output schema, the description covers the action, scope, output format, use case, and how to source the parameter. The one notable omission is guidance on when list_dns_records would be the better choice over this bulk-export tool, though this is minor given the tool's simplicity.

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 100% and the zone_id property already documents the env-var fallback. The description adds value beyond the schema by instructing the agent how to obtain a valid zone_id ('Call list_zones first to resolve a domain name to a zone_id'), which is dynamic guidance the static schema cannot provide. That elevates it above the baseline of 3.

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 first sentence names a specific verb (export), a specific resource (all DNS records for a zone), and the output format (JSON array), which is far more specific than a generic phrase. The 'all records' scope and the backup/bulk use case implicitly distinguish it from siblings like list_dns_records, and it is clearly the inverse of import_dns_zone, so an agent can select it without opening any schema.

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 states an explicit use case ('Useful for backups and bulk operations') and gives a concrete prerequisite workflow ('Call list_zones first to resolve a domain name to a zone_id if needed'). It does not name alternatives or state when not to use it (e.g., when to prefer list_dns_records for interactive inspection), so it provides clear context but no exclusions.

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