shodan_host

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 known. The description adds the scope of returned data (ports, services, etc.) but does not disclose any additional behavioral traits such as rate limits, response size, or historical depth beyond what the schema hints at. This meets the baseline but does not exceed it.

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 sentence, front-loads the core purpose ('Get all information about a specific IP'), and every word contributes value. No redundancy or filler.

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 read-only nature confirmed by annotations and a fully documented schema, the description is sufficient to set expectations for a basic lookup. It enumerates key data categories but does not detail output structure or pagination, which is acceptable since there is no output schema and the parameter descriptions already cover maxResults.

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?

All parameters are fully described in the schema (coverage 100%), so the description adds no extra parameter meaning. The baseline of 3 applies because the schema already carries the burden, and the description does not compensate further.

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 tool retrieves all information about a specific IP, which is a distinct resource from sibling tools like shodan_search or shodan_dns_resolve. The verb 'Get' is specific and the scope is unambiguous, making the purpose immediately obvious.

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 implicitly indicates when to use this tool: when you have a specific IP address and want comprehensive details. It does not explicitly name alternatives or provide exclusions, but the context is clear enough for an agent to select this over search-oriented siblings.

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