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

readOnlyHint=true and the description is consistent with a safe read. Beyond annotations, it discloses that the resource is a single zone and that the payload is a plain-text BIND zone file, plus the underlying HTTP endpoint. It doesn't discuss size limits or truncation for large zones, so not a 5.

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?

One sentence, front-loaded with the action and output format, with rationale and endpoint appended compactly. No filler.

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?

No output schema exists, and the description compensates by naming the return artifact (BIND zone file, plain text), which is the key thing an agent needs to know here. A one-parameter read-only export needs little more, though size limits or a note on zone selection would round it out.

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 100% for the single zone_id parameter, so the schema already documents the input. "Export one DNS zone" only implies zone_id scoping, adding little beyond the schema — baseline 3 when the schema does the work.

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?

States a specific verb (export), resource (one DNS zone), and concrete output format (BIND zone file, plain text), which is enough to separate it from sibling reads like bunny_get_dns_zone (structured) and bunny_list_dns_records. The API endpoint reference (GET /dnszone/{id}/export) reinforces the operation.

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?

Gives clear use contexts — "review, diffing or backup before a change" — which tells the agent when this is the right tool. It stops short of naming an alternative or an exclusion (e.g., use bunny_get_dns_zone for JSON/structured data), so no explicit when-not guidance.

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