shodan_search

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

No annotations are provided, so the description carries the full burden. It only states 'Search Shodan for internet-connected devices,' which implies a read operation but does not disclose behavioral traits such as API key requirements, rate limits, pagination behavior, or what happens with large result sets. The minimal description fails to inform the agent about critical operational details.

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, which is concise but under-specified. It front-loads the core purpose, but the brevity sacrifices necessary details. While conciseness is valued, the structure lacks the depth needed for a tool with no annotations and no output schema.

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 absence of annotations and output schema, the description is incomplete. It does not explain the return format, pagination, or how to handle the optional parameters. For a tool with 3 parameters and no schema descriptions, the agent requires more contextual completeness to use it effectively.

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 has 3 parameters with 0% description coverage in the schema, and the description adds no information about any parameter. It does not explain what 'query' should be (e.g., Shodan search syntax), what 'page' is for (pagination), or what 'api_key' is used for. With no schema descriptions and no parameter semantics in the description, the agent has no guidance on how to fill parameters correctly.

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 searches Shodan for internet-connected devices, which is a specific verb and resource. However, it does not differentiate from sibling tools like shodan_host_info or shodan_stats, which are distinct operations. The lack of differentiation prevents the agent from knowing when to use this search versus other Shodan tools.

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?

No usage guidelines are provided. The description does not mention when to use this tool versus alternatives (e.g., shodan_host_info for a specific IP), nor does it specify any prerequisites or context for invoking the tool. The agent receives no guidance on when or when not to use it.

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