dns_lookup

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

No annotations are available, so the description must disclose behavioral traits. It does mention the cost ($0.001 USDC), which is a useful side effect, but it does not describe what the tool does beyond the implied lookup, whether it makes network requests, or how data is handled. This is very thin behavioral disclosure.

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 very brief, which helps conciseness, but it is under-specified. It includes useful context like cost and security/network category, yet restates 'dns lookup' with little additional value. It is not well-structured to support tool selection.

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?

With no annotations, no output schema, and a generic input schema, the description is far too minimal to guide proper use. The agent cannot infer required inputs, return values, or usage constraints, making it almost completely inadequate.

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 only defines a generic 'params' object with no specific properties, so the description needed to explain what parameters are expected (e.g., domain name, record type). It does not, leaving the agent with no information about how to construct the invocation.

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 'dns lookup' which restates the tool name, and adds a vague category 'Security & Network tool'. This gives a minimal sense of purpose but does not specify what kind of DNS lookup (e.g., A, MX, TXT records) or how it differs from sibling tools like reverse_dns_lookup or dns_whois_lookup.

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?

No usage guidance is provided. The description does not mention when to use this tool versus alternatives such as reverse_dns_lookup or whois, nor any prerequisites, scenarios, or context where it would be the appropriate choice.

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