list_dns_records

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

Annotations already provide readOnlyHint and openWorldHint. The description adds filtering capability but does not elaborate on pagination behavior (default page/per_page), rate limits, or the fact that fetch_all auto-paginates. 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?

The description is a single, front-loaded sentence with no redundancy. Every word adds value, making it appropriate in length.

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?

Despite having 6 parameters and no output schema, the description does not explain return format, default pagination, or edge cases (e.g., empty results). The openWorldHint annotation signals partial results, but the description lacks completeness for a full understanding.

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 67%, with descriptions for zone_id, type, name, and fetch_all. The tool description does not add any parameter-specific meaning beyond what the schema already provides. Missing descriptions for page and per_page are not addressed.

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 of a zone, with optional filtering by type/name. This verb-resource combination is specific and distinguishes it from sibling tools like create_dns_record or delete_dns_record.

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 implies usage for listing DNS records but gives no explicit guidance on when to use this tool versus alternatives like export_dns_records or when pagination is needed. It lacks when-not-to-use or when-to-prefer-other-tools context.

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