list_dns_records

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

Annotations already mark the operation read-only, and the description adds context beyond that: records come from GoDaddy's authoritative nameservers, support type/name filtering, and include the recordId needed for mutations. No contradiction with annotations.

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 short sentences front-load the main purpose, then add the most decision-relevant details: filtering and recordId. No filler beyond the acceptable one-word 'Read-only' summary, which reinforces the safety profile.

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 a list operation with pagination parameters already documented in the schema, and the description covers the key return value (recordId) and the filtering model. There is no output schema, so a bit more detail about the response shape/pagination would help, but the existing details are enough for correct invocation.

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?

Input schema covers all parameters with descriptions, so the baseline is 3. The description mentions filtering by type and/or name and explains @ as zone apex, but this largely mirrors the schema and adds no deeper parameter semantics such as precedence or mutually exclusive combinations.

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 clearly states a specific action ('List DNS records'), a resource ('domain hosted on GoDaddy'), and a filtering capability, which distinguishes it from sibling tools like list_domains, add_dns_record, and update_dns_record. It also conveys that the result includes recordId for later updates/deletes, reinforcing its role.

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?

The description tells the agent when the tool is useful by noting the recordId is needed to update or delete records and by stating filtering options. It does not explicitly preclude alternatives, but the read-only framing plus sibling context make the intended use clear.

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