shodan_search

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

No annotations are present, so the description must fully disclose behavior. It only says 'Search' with no mention of authentication requirements, rate limits, or whether results are limited. The description fails to inform about important behavioral traits beyond the mute schema.

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 short sentence, which is concise but lacks necessary depth. It could benefit from additional context without becoming wordy, so it is adequate but not optimal.

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 presence of 6 parameters and an output schema, the description is incomplete. It does not explain return values, pagination behavior, or how the query syntax works relative to the SHODAN website. The output schema exists but is not referenced or summarized.

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 100%, and the input schema provides detailed descriptions for each parameter (query, page, limit, etc.). The tool description adds no additional meaning, achieving the baseline score for high-coverage schemas.

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 states 'Search the SHODAN database,' which is a clear verb+resource, but it lacks specificity to distinguish from sibling tools like shodan_search_cursor, shodan_host, or shodan_exploits_search. The purpose is vague for an agent choosing among similar 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 guidance is provided on when to use this tool versus alternatives such as shodan_search_cursor (for cursor-based pagination) or shodan_search_tokens (for token searches). The agent receives no context for appropriate use.

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