batch_dns_lookup

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

With no annotations, the description carries the full burden. It mentions the return structure (per-query records, success/fail counts, summary) but lacks details on rate limits, error handling, or authentication. This is adequate but not thorough.

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 with three short sentences plus Args/Returns sections. It is front-loaded with the purpose and provides structured information without unnecessary words.

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 low complexity (2 params, no output schema), the description covers purpose, parameters, and return structure. It could mention the sibling 'dns_lookup' for single queries, but overall it is sufficiently complete.

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 input schema has 0% description coverage, but the description adds meaning by explaining 'queries' as a list of hostnames and 'record_type' as DNS record type with default A. This compensates for the schema gap, though it could be more detailed (e.g., hostname format, limits).

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 performs DNS lookups for multiple hostnames at once, using a specific verb and resource. It distinguishes itself from the sibling tool 'dns_lookup' which handles single queries.

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 explicitly says to use this tool when resolving multiple hostnames or checking DNS records for several domains, providing a clear context. It does not explicitly exclude single lookups, but the context implies batch use.

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