Forward DNS

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

Annotations already declare readOnly, idempotent, open-world and non-destructive, so safety is covered. The description adds no behavioral context beyond input format — nothing about how unresolvable hostnames are reported, batch limits, or rate limiting, which matters for an open-world lookup service.

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?

Two short sentences, front-loaded with the operation and followed by the input format; nothing is wasted. It is arguably too terse for the remaining gaps, but on structure and brevity alone it is efficient.

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?

For a one-parameter read-only lookup with annotations covering safety, the minimum is present. Missing are the failure semantics (what happens to a hostname that doesn't resolve) and any hint about response shape, which would help since there is no output schema.

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 coverage is 0% and the single parameter is a bare string with only minLength, so the description's 'comma-separated list' is genuinely additive — it tells the agent the string is a batch container rather than one hostname. It still lacks constraints such as maximum entries or accepted hostname syntax.

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?

States a specific verb and resource: 'Resolve hostnames to IPs', which is unambiguous on its own. It does not, however, distinguish itself from the inverse sibling shodan_dns_reverse or from shodan_dns_domain, so an agent must infer the direction/scope distinction.

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 only usage information is input formatting ('comma-separated list'). There is no guidance on when to use this versus shodan_dns_reverse, whether batches are preferred over single lookups, or limits on list size.

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