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

Annotations already declare readOnlyHint=true, openWorldHint=true and destructiveHint=false, so safety is covered. The description adds genuinely new behavior on top of that: the pagination loop via next_page.after/offset and the shape of returned zone records. It stops short of auth/rate-limit or default page-size details.

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?

Three compact sentences that are front-loaded with the resource and returned fields, then the pagination rule, then the endpoint. No filler, no repetition of the title.

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 low-complexity, parameterless list tool with no output schema, the description compensates by enumerating returned fields and explaining the pagination cursor flow, which is everything an agent needs to call and iterate it correctly.

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 the schema already explains limit (1-1000, omit for default) and the after/offset cursors. The description's 'call again with its after/offset' restates the schema rather than adding format or edge-case detail, 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?

States a specific verb and resource ('List the DNS zones in the account') and enumerates what each entry contains (name, id, TTL/SOA settings, primary/secondary setup, linked zones, tags). This clearly separates it from the singular sibling ns1_get_zone and from the search tools, and the trailing 'GET /v1/zones' pins the resource precisely.

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 an explicit operational rule: 'If next_page is not null, call again with its after/offset to get more,' which tells the agent exactly how to continue an incomplete listing. It does not, however, say when to prefer this over ns1_get_zone or ns1_search, so the selection guidance is incomplete.

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