list_dns_records

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

With no annotations provided, the description carries the full behavioral disclosure burden. It honestly discloses the 'all records' scope, which implies an unbounded result set, and hints at the zone_id configuration workflow. However, it does not describe return format, pagination, or potential response-size implications, which are relevant for an 'all' query with no annotation safety net.

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 sentences with zero waste: the primary action is front-loaded in the first sentence, and the second sentence provides the prerequisite workflow that earns its place. No redundant restatement of the name or schema fields.

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 simple list tool with three optional parameters and no output schema, the description covers the core action and the zone_id acquisition flow adequately. It omits only minor behavioral notes like pagination expectations for large zones, which are not essential for correctly selecting or invoking the tool.

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%, so the baseline is 3. The description adds value beyond the schema by explaining how to obtain zone_id via list_zones, supplementing the schema's note about the CLOUDFLARE_ZONE_ID env var. The name/type filters are already fully documented in the schema and need no repetition.

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 states a specific verb and resource — 'List all DNS records for a zone' — which clearly scopes the operation to zone-level enumeration. This distinguishes it from siblings by action (create/update/delete are mutations), by granularity (get_dns_record is singular), and by object type (list_zones lists zones, not records).

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 gives an explicit usage prerequisite: 'Call list_zones first to resolve a domain name to a zone_id if needed,' which tells the agent how to prepare the required context for this tool. However, it does not explicitly state when to prefer this over get_dns_record or mention exclusions, stopping short of full when/when-not guidance.

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