Export zone file

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

Annotations mark this as readOnlyHint=true, which aligns with the export operation. The description adds that it exports the full contents in BIND format, but does not clarify details like whether the output is plain text or includes all record types, or if special zones are excluded. No contradiction, but limited additional transparency.

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 sentence, concise and front-loaded with the action ('Export') and resource ('DNS zone'). It omits no critical context but is adequately structured and not verbose.

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?

Given the simple nature of this tool (single parameter, no output schema, read-only), the description is sufficient for an agent to understand the action. However, for a tool that returns a specific format, some context on the output evolution or access requirements could enhance completeness, but not critically needed here.

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%, with the single 'zone' parameter already documented as 'ID or name of the zone'. The description does not add any further parameter details beyond the schema, but the baseline of 3 is acceptable given full schema description, so a 3 is appropriate.

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 tool exports a DNS zone's full contents in BIND zone file format, which is a specific and distinct action among siblings like get_zone and import_zonefile. It does not explicitly distinguish from get_zone, but the action is unambiguous.

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 usage for exporting zone data, but does not provide explicit guidance on when to use this tool versus alternatives like get_zone or import_zonefile. No when-not-to-use or alternative references are given, so guidance is only implicit.

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