List DNS zones

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

Annotations already declare readOnlyHint=true, destructiveHint=false and a closed-world scope, so the safety profile is covered. The description adds useful context beyond them: the required dns:read permission and that the listing is scoped to the account's forward zones rather than a single zone.

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 sentences, zero filler, with the core purpose front-loaded and the permission caveat second. Nothing is repeated from the schema or annotations.

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 a fully documented schema and clear annotations, the description covers purpose, scope, and the auth requirement; no output schema exists but return shape is a straightforward list. Only a note on pagination behavior (already in the schema) and an alternative-tool pointer are absent.

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%, with both page and snapshot fully documented (including snapshot reuse and restart-on-membership-change semantics), so the schema does the heavy lifting. The description adds nothing about pagination parameters, matching the baseline for high-coverage schemas.

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 and resource ('List forward DNS zones') and narrows scope with 'forward' and 'on the account', which an agent can distinguish from get_dns_zone (single zone) and list_dns_templates (templates). It does not explicitly name a sibling or contrast itself, so it falls short of the top band.

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 by the verb 'List', and the description adds a real prerequisite ('Requires dns:read when using an API key'), which helps an agent know the call may fail without that scope. There is no explicit when-to-use/when-not-to-use guidance or pointer to alternatives such as get_dns_zone.

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