Export DNS (BIND)

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

No annotations are provided, so the description must disclose behavior. It mentions exporting as a BIND zone file, which implies a read-only operation, but does not explicitly state safety (e.g., no modifications). It lacks details on authentication requirements beyond the account key or rate limits.

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?

The description is a single, clear sentence that front-loads the main action and purpose. It is efficient, but it omits some useful context that could be added without bloat.

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?

The tool is simple, and the description covers the main purpose and output format. However, without an output schema, it does not explain the structure of the zone file or any limitations (e.g., size). For a backup tool, this is somewhat adequate but not comprehensive.

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?

The input schema has 100% coverage (both parameters have descriptions in schema: 'Zone domain' and 'Cloudflare account key'). The description adds context about the output format ('BIND zone file') but does not enhance parameter understanding beyond the schema, earning a baseline 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 description clearly states 'Export all DNS records for a zone as a BIND zone file', specifying the verb (Export), resource (DNS records), and output format (BIND zone file). This distinguishes it from siblings like cf_dns_list (list in different format) or cf_dns_add (add records).

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 phrase 'good for backups' implies a backup use case, but there is no explicit guidance on when not to use it or alternatives for other scenarios (e.g., individual record management). The guideline is implied but not fully explicit.

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