dns_list_zones

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

readOnlyHint=true already signals a safe read, so the description's added value is the disclosure that results include registrar nameserver settings and available record types, plus the required scope 'dns:read'. It says nothing about result size, pagination, or behavior for accounts with no zones.

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?

A single sentence with no filler; the resource and the payload contents are front-loaded, and the scope is appended last where it belongs. Nothing is repeated or 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 input parameters, no output schema, and annotations covering the safety profile, the description supplies the main missing piece: what the response conceptually contains. Only minor operational details (pagination, empty-state behavior) are absent, which is acceptable at this complexity.

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?

The tool takes zero parameters, so the schema carries no semantic load and the baseline is a 4. The description correctly implies no filtering inputs are needed.

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?

Names the resource (DNS zones on the free tport.cloud nameservers) and the associated data returned (nameservers to set at the registrar, offered record types), which is enough to distinguish it from the record-level siblings dns_add_record/dns_delete_record. The verb is implicit rather than stated, so it falls short of the verb+resource precision a 5 requires.

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?

There is no explicit when-to-use statement and no reference to alternatives such as dns_get_zone for a single zone or dns_add_zone. For a zero-parameter listing tool the intent is inferable, but the description does not route the agent among siblings.

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