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

Annotations already establish readOnlyHint=true, so safety is covered; the description adds the substantive behavioral detail that the payload is a plain-text BIND zone file rather than structured JSON, plus the underlying endpoint. It does not discuss size limits or pagination, but for a read-only export that is a minor omission.

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 tight sentence plus the endpoint reference; the output format and the motivating use cases are front-loaded and nothing is wasted.

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?

With no output schema, the description usefully discloses the return type (plain-text BIND zone file) and the mutation risk is nil per annotations. It is essentially complete for a single-parameter read tool, though it could note the response's non-JSON shape explicitly for downstream parsing.

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% and there is a single parameter (zone_id), so the schema already carries the parameter meaning. The description adds no syntax, format, or lookup guidance for the ID beyond what the schema states, making the baseline of 3 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?

States a specific verb (Export), a specific resource (one DNS zone), and the output format (BIND zone file, plain text). This clearly separates it from bunny_get_dns_zone and bunny_list_dns_records, which do not produce a zone-file export.

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 concrete use cases — review, diffing, backup before a change — which tells the agent when this tool is the right pick. It stops short of naming alternatives (e.g. use get_dns_zone for JSON inspection), so it is not a full when/when-not routing statement.

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