shodan_dns_resolve

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the 'forward DNS lookup' clarification, but it does not mention return format, rate limits, or other behavioral details. It is consistent with annotations and provides modest value beyond them.

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 a single, focused sentence that presents the verb and resource first. There is no redundant information, making it exceptionally concise and well-structured.

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 DNS lookup tool, the description, schema, and annotations together provide sufficient context. The only minor gap is not specifying the output format, but no output schema is provided and the core behavior is clearly communicated.

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 already documents the only parameter with a concrete format and example. The description adds no additional parameter semantics. With schema description coverage at 100%, the baseline of 3 is appropriate.

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 clearly states the action ('Resolve'), the object ('hostnames'), and the output ('IP addresses'). The parenthetical '(forward DNS lookup)' explicitly distinguishes it from the reverse DNS sibling (shodan_dns_reverse), making the purpose unambiguous.

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 'forward DNS lookup' phrase implies when to use this tool (hostname→IP) versus a reverse lookup, but it does not explicitly name alternatives or state when not to use it. This is clear context without exclusions, meeting the criteria for a 4.

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