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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only says it queries all DNS record types, but doesn't disclose what the output looks like, whether it performs multiple queries, whether it's rate-limited, whether it requires a domain vs. an IP, or what happens on failure. The output schema exists but the description doesn't explain the behavior beyond the basic query.

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 short sentence, which is concise and front-loaded. It states the core action immediately. However, it is under-specified for a tool with no annotations and a single generic parameter, so the conciseness is not fully effective.

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 has no annotations, one generic parameter, and a large set of DNS-related siblings, the description is incomplete. It doesn't explain what 'q' should be, what output to expect, or how this tool differs from dnsquery, dns, dnsmx, etc. The output schema exists but the description doesn't provide enough context for an agent to select and invoke this tool correctly.

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 0%, and the only parameter is 'q' with a default of empty string. The description doesn't explain what 'q' should contain (domain, hostname, IP?). The name 'q' is generic, and the description's 'DNS record types' implies a domain, but this is not explicit. The description adds minimal meaning beyond the schema.

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: 'Query ALL DNS record types at once.' This is clear about what the tool does, but it doesn't distinguish it from the many DNS-related siblings like dns, dnsquery, dnsmx, dnssec, dnsverify, dnsgraph, etc. The phrase 'ALL DNS record types' hints at a broad query, but the description doesn't explicitly differentiate it from those alternatives.

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 versus the many DNS siblings. The description implies a broad DNS query use case, but it doesn't state when to prefer dnsrecon over dnsquery, dns, dnsmx, or others. No exclusions or alternative routing are provided.

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