shodan-dns-resolve

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

No annotations are provided, so the description carries the full burden. It adds the prerequisite of a Shodan API key and states the return type (DnsResolveResult). However, it does not disclose whether the operation is read-only, any rate limits, error behavior, or whether it consumes API quota. For a simple DNS lookup, some of this may be implicit, but the description lacks thorough behavioral context.

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 four short sentences that front-load the purpose. Every sentence earns its place: purpose, use case, prerequisite, and return type. No redundancy or fluff.

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, the presence of an output schema, and full parameter descriptions, the description is largely complete. It adds the API key requirement and a workflow suggestion. It lacks edge-case behaviors like error handling or rate limits, but these are not critical for a basic DNS resolution tool.

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 100% coverage with descriptions for both 'hostnames' and 'timeout'. The tool description does not add any parameter-specific details beyond what the schema already provides, so it meets the baseline for high schema coverage. No additional meaning is supplied.

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 opens with a clear, specific verb and resource: 'Resolve hostnames to IP addresses using Shodan's DNS service.' This immediately distinguishes the tool from the sibling shodan-dns-reverse (which resolves IPs to hostnames) and other lookups. The additional context about mapping domain names before IP lookups reinforces its purpose.

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 provides a clear usage context: 'Useful for mapping domain names to IPs before performing IP lookups.' This tells the agent when to use it, but it does not explicitly mention when not to use it or name alternative tools. No exclusions, but the context is clear enough.

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