Reverse DNS

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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description contributes only the batching detail (comma-separated list) and says nothing about rate limits, behavior on unresolvable IPs, or result format — modest added value over the annotations.

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 with zero waste, and the core purpose is front-loaded before the input-format note. Nothing could be cut without losing 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?

There is no output schema, so the description should say something about the returned shape (e.g., IP-to-hostname mapping) and how unresolvable IPs appear — neither is covered. For a simple lookup tool with good annotations this is adequate but noticeably thin on the return side.

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 `ips` parameter is an undescribed string, so the description's "comma-separated list" is genuinely load-bearing and conveys multi-IP input that the schema cannot. It stops there, though — no guidance on limits, whitespace, or invalid entries — so it only partially compensates for the coverage gap.

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?

"Resolve IPs to hostnames" gives a specific verb and resource, making reverse DNS clearly distinct from forward lookups like shodan_dns_resolve or shodan_dns_domain. It never names those siblings explicitly, so differentiation relies on the agent's own inference.

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 states what the tool does but gives no when-to-use framing, no prerequisites, and no mention of the closely related shodan_dns_resolve or shodan_dns_domain siblings. The agent must infer that this is the reverse-DNS path when it holds IPs rather than hostnames.

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