shodan_host_info

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

No annotations are provided, so the description must fully disclose behavioral traits. It only says 'Get... information' without explaining what information is returned, whether it is a read operation, rate limits, or authentication requirements. This is insufficient for an agent to understand side effects or restrictions.

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, concise sentence that front-loads the core purpose. However, it lacks structure and does not include additional sections for parameters or usage, making it too minimal to be considered 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?

Given the lack of output schema and annotations, the description is severely incomplete. It does not explain the return format, possible errors, or how the output relates to the input. For a tool with two parameters, this is inadequate for complete understanding.

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 description coverage is 0%, meaning the schema provides no descriptions for the two parameters (ip, api_key). The tool description does not add any meaning beyond parameter names. It fails to explain that 'ip' requires a valid IPv4 address or that 'api_key' is for authentication, leaving ambiguity.

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 ('Get') and the resource ('Shodan information for a specific IP address'). It is not a tautology and provides a clear purpose. However, it does not differentiate from sibling tools like shodan_search or shodan_stats, which might also return host-related information.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that it is specifically for a single IP or that shodan_search might be more appropriate for broader queries. No exclusions or usage context are provided.

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