dns_list_records

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

Without annotations, the description must fully disclose behavior. It mentions filtering by zone_id but omits pagination details (despite page and per_page parameters) and does not clarify if leaving zone_id null lists all records across all zones. No side effects or ordering are described.

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?

The description is very concise, using a single sentence with no redundancy. However, it sacrifices informativeness for brevity, missing key details about pagination and default behavior. Still, it is well-structured and front-loaded.

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?

Given 3 parameters (with pagination) and no required fields, the description should explain default listing behavior and how pagination works. The output schema exists, so return values are covered, but the overall context of the listing operation (e.g., maximum results, ordering) is absent.

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 coverage is 0%, so the description must explain all parameters. Only zone_id is mentioned (as a filter). The page and per_page pagination parameters are completely undocumented in the description, leaving their purpose and behavior unexplained.

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 the tool lists DNS records, with optional filtering by zone. This distinguishes it from sibling tools like dns_list_zones (lists zones) and dns_get_record (gets a single record). The verb 'List' and resource 'DNS records' are specific and unambiguous.

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 on when to use this tool versus alternatives such as dns_get_record for a single record or dns_export_zone_file for zone-level exports. The description does not mention prerequisites, typical use cases, or limitations.

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