list dns records

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

Annotations already declare the operation read-only, idempotent, and non-destructive, so the description does not need to restate those. It adds only the implementation note about 'verified command v-list-dns-records', which provides no additional side-effect, permission, or pagination context.

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 with the core statement first. The second sentence is extra implementation detail but does not harm; a 5 would require every sentence to add necessary information.

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 listing tool with rich annotations and an output schema, the description is minimally sufficient. However, it lacks parameter semantics and routing guidance to sibling tools, so it is not fully complete.

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 0%, and the description says nothing about 'user', 'domain', or 'format'. An agent gets no help understanding that 'user' is the account owning the zone or that 'domain' is the zone name.

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?

Description states a clear action ('List') and resource ('records in a DNS zone'), distinguishing it at a glance from sibling tools like list_dns_domains and get_dns_domain. It does not explicitly name a sibling or exclusion, so it falls short of a top score.

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?

No guidance on when to use this instead of list_dns_domains or get_dns_domain, and no prerequisites or exclusions are mentioned. The only implied context is the general statement that it lists records in a DNS zone.

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