domain_fetch_dns_records

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, and openWorldHint. The description adds value beyond annotations by disclosing the data source ('Verified source: Cloudflare DoH'), caching behavior ('4-hour cache'), and the read-only, side-effect-free, idempotent nature. No contradictions 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 concise but comprehensive. It front-loads the core purpose and important characteristics (read-only, idempotent), then provides parameter details, usage comparison, source, caching, and fallback. Every sentence adds value without repetition.

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 the tool's complexity (fetching DNS records), annotations (readOnly, idempotent), and existing output schema, the description covers all necessary aspects: purpose, parameters, usage context, data source, caching, and fallback. It leaves no gaps for an AI agent to misuse.

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 100% of parameters with descriptions. The description adds further clarity by providing examples ('e.g. cloudflare.com'), listing valid record types, and giving an example array. While the schema already describes the parameters, the description enriches them with practical usage details.

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 fetches current DNS records for a domain via Cloudflare DNS over HTTPS. It uses specific verbs ('Fetch', 'resolve') and explicitly names the resource ('DNS records for a domain'). It also differentiates from the sibling tool domain_fetch_domain_rdap by contrasting DNS records vs registration metadata.

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 provides explicit guidance on when to use this tool ('when you need live DNS resolution') and when not to ('Use domain_fetch_domain_rdap instead when you need registration metadata'). It also includes a fallback instruction to call report_feedback if the tool does not serve the user's need, demonstrating thorough usage guidance.

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