cloudflare_dns_export

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

No annotations provided, so the description carries full burden. It mentions returning raw text in BIND format, which is helpful, but does not disclose potential size limits, rate limiting, or error handling behavior for invalid zone IDs.

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 two short sentences with no filler. Every word adds value: verb, resource, format, return type. Perfectly concise.

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 simple export tool with one parameter and no output schema, the description covers the core functionality. It explains what the output is (BIND format raw text). However, it lacks details about the response structure or error conditions, which might be needed for a fully complete description.

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 already has 100% coverage with a clear description of zone_id (allowing ID or name). The description adds no additional context beyond 'all DNS records' and the output format, so it meets but does not exceed the baseline.

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 action (Export), the resource (all DNS records for a zone), the output format (BIND zone file format), and the return type (raw text). This distinguishes it from siblings like cloudflare_dns_list which returns JSON.

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?

No explicit guidance on when to use this tool versus alternatives like cloudflare_dns_list or cloudflare_dns_get. The description implies usage for bulk export/backup, but does not mention scenarios or exclusions.

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