dns_bulk

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 disclosing behavior. It only states the basic query action and gives no details on error handling, partial failures, rate limits, return format, or whether any restrictions apply. For a bulk tool, this lack of transparency about per-domain behavior is a significant gap.

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 concise sentence that gets straight to the point. No wasted words or redundant information.

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?

Although the tool is relatively simple, the description omits crucial context for a bulk operation: what the response structure looks like, how errors are handled if some queries fail, and whether all record types are supported. With no output schema and no annotations, this brevity leaves the agent under-informed.

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 already provides descriptions for both parameters, achieving 100% schema coverage. The description adds no extra meaning about parameter semantics, such as accepted record_types values or resolver format. Per calibration, baseline is 3 when schema coverage is high, and the description does not surpass that.

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 action ('Query'), the resource ('DNS records'), and the scope ('for multiple domains in one call'). It effectively distinguishes from siblings like dns_lookup (single domain) and dns_reverse (reverse lookups).

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 implies batch usage ('multiple domains in one call') but does not explicitly state when to use this tool over alternatives, nor does it mention exclusions (e.g., for single-domain lookups use dns_lookup). The sibling tool names are not referenced, so guidance is only implied.

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