web_dns_lookup

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

No annotations are present, so the description should fully convey behavioral traits. It mentions the operation (DNS resolution) but lacks details on potential side effects (no destructive actions, but not stated), rate limits, or return value structure. For a read-only informational tool, this is a 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 front-loads the action and enumerates supported record types. No excess words; every part serves a purpose.

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's simplicity (2 parameters, no output schema), the description covers the core purpose and types. However, it does not indicate the output format or error behavior, leaving some context incomplete.

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 100% with both 'domain' and 'rrtype' well-described. The description in the tool text reiterates the domain and record types but adds no new semantics beyond the schema. Baseline 3 is appropriate.

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 explicitly states 'Perform DNS resolution for a domain' and lists specific record types (A, AAAA, MX, etc.), clearly indicating the tool's purpose and scope. It is distinct from sibling tools like web_ssl_check or network utilities.

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 does not provide explicit guidance on when to use this tool versus alternatives, but the domain is narrow and no sibling directly overlaps. Implicitly, it is for DNS lookups, but lack of 'when-to-use' or 'when-not-to-use' reduces clarity.

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