domain_fetch_dns_records

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

Without annotations, the description states it returns 'all matching DNS records currently in effect', which is useful. However, it lacks details on error behavior or rate limits, making it adequate but not comprehensive.

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 front-load the purpose and parameters, with no wasted words. It efficiently covers what the tool does, what to provide, and what it returns.

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 output schema exists, so return details are covered elsewhere. However, the description omits error conditions and has a contradiction about parameter requiredness, making it incomplete for safe 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?

The description adds meaning by listing example record types (A, MX, TXT) and stating the record type is optional, but contradicts the schema which requires 'record_types'. This reduces clarity and trust.

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 DNS records for a domain, using the verb 'get'. It distinguishes from sibling tools like domain_fetch_domain_history or domain_fetch_ssl_certificate_chain by specifying 'DNS 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 directly says 'Use this to get DNS records', which implies its purpose, but provides no guidance on when not to use it or alternatives among siblings.

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