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

Annotations already declare readOnlyHint=true, so the safe-read profile is covered. The description adds the useful detail that each zone includes nameserver detection, DNSSEC and logging status, but says nothing about pagination behavior or the API endpoint context beyond the bare route.

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?

Two short clauses, front-loaded with the action and resource, with the returned fields following. The trailing 'bunny.net: GET /dnszone' is terse and useful; no wasted sentences.

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 read-only list tool with full schema coverage and no output schema, the description covers purpose and the nature of returned data. It stops short of routing guidance among the many sibling list/get tools, which would complete it.

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%, so the schema fully documents page, search, and per_page with ranges and defaults. The description adds no parameter semantics beyond what the schema already provides, so the baseline 3 applies.

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?

Clear verb+resource ('List the DNS zones hosted on bunny.net') and it enumerates the fields returned (nameserver detection, DNSSEC, logging status). It does not explicitly distinguish from bunny_list_dns_records or bunny_get_dns_zone, though 'zones' vs 'records' is reasonably self-evident.

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?

Usage is implied (use to list DNS zones) but there is no explicit guidance on when to use this versus bunny_list_dns_records, bunny_get_dns_zone, or bunny_export_dns_zone. No exclusions or conditions stated.

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