search_shodan

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

With no annotations provided, the description carries full responsibility. It discloses credit consumption, explicit pagination (one page, up to 100 services), the semantics of the limit parameter (caps evidence, not credits), and the lack of automatic pagination/retries. This is thorough behavioral disclosure.

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 concise, with the core purpose front-loaded in the first sentence and behavioral details in a separate paragraph. No redundant or filler content exists; every sentence adds value.

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?

The description adequately covers purpose, behavior, and key parameter semantics, which is sufficient for a search tool lacking annotations and output schema. Minor gaps include exact query syntax and response format, but these are not critical for correct invocation.

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 coverage is 0%, so the description must compensate. It adds meaning to 'limit' (caps returned evidence, not credits) and implies 'page' via 'one explicit page'. However, the 'query' parameter is only referenced as 'native filters', leaving syntax to the user's knowledge. This is partial compensation.

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 verb 'Search', the resource 'Shodan's indexed services', and the method 'using native filters'. This distinguishes it from siblings like search_web or search_username by specifying the Shodan platform.

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?

It provides clear context for when to use the tool (searching Shodan with native filters) but does not explicitly mention alternatives or when not to use it. Given siblings like lookup_shodan_host, a brief differentiator would help, but the description's specificity suffices for basic routing.

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