dnslookup

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

Discloses use of DoH for privacy, ability to switch to UDP, and return format including TTL. No annotations provided, so description carries full burden; adequately covers behavior for a read-only tool.

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?

Five concise sentences, front-loaded with purpose, no 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?

Covers all key aspects: supported record types, query methods, and return data (TTL). No output schema needed; description sufficiently explains output.

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 covers all parameters with descriptions; description adds context on why to use DoH (privacy, bypass filters) and the default endpoint (Cloudflare), enhancing understanding beyond 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?

Clearly states 'Query DNS records for a hostname' and lists supported record types. Distinct from sibling tools as it handles DNS specifically.

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?

Explains two modes (DoH and traditional UDP) with rationale for each, but does not explicitly contrast with alternative tools like using bash/ dig.

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