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

No annotations are provided, so the description must disclose behaviors such as rate limits, whether it performs live lookups, returns historical data, or requires authentication. The description provides none of this. It does not even state that it queries DNS servers.

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 (one line) and lists record types, but it lacks a verb and actionable information. It is under-specified rather than efficiently short. Front-loading is present, but the content is mostly a catalog.

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 an output schema exists, the description should fully explain how to request records and what the output represents. It fails to mention the input format, expected output structure, or any constraints. An agent cannot reliably call this tool without additional inference.

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 has only one parameter 'q' with no description, and schema description coverage is 0%. The description does not clarify what 'q' is (domain name? record type?) or provide expected format. It only mentions record types, which might be related but not explicit.

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 lists record types but does not state what the tool does (e.g., 'Retrieve', 'Lookup', 'Resolve'). It is a vague label: 'DNS Records: ...' could mean fetch records, validate, or enumerate. It does not distinguish from many siblings like dnsquery, dnsrecon, dnsmx, or dnssec.

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?

There is no guidance on when to use this tool vs. alternatives. It doesn't specify a use case like 'lookup DNS records for a domain' or when to choose dnsquery over this. The sister tool list is huge with many DNS-related options, but no exclusions or preference conditions are given.

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