adm_dns_records

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It states that the tool lists records, but it does not disclose whether the operation is read-only, what the response shape is, whether pagination or filtering applies, or what happens if the domain does not exist.

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?

One sentence, no filler, and the core action and object are front-loaded. Every word earns its place.

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?

The tool is simple with one documented parameter, but the absence of any usage guidance, behavioral caveats, or return-format description leaves noticeable gaps. An agent can infer the basic operation from the schema and purpose, but the description alone is only minimally 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 100%, and the single parameter domain_id is documented with 'Domain ID (from adm_domains)'. The description itself adds no parameter-specific meaning, so the baseline score of 3 is appropriate since the schema already explains the parameter.

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?

The description uses a specific verb ('List') with a clear resource ('all DNS records') and scope ('for a domain'). It is immediately distinguishable from write-oriented siblings like adm_dns_add and adm_dns_delete, and from domain-level tools like adm_domains.

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 is provided about when to use this tool versus alternatives, such as adm_dns_add or adm_dns_delete. The only usage signal is the verb 'List', but the description does not mention prerequisites, exclusions, or conditions that would route an agent to a sibling.

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