shodan_exploits_search

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

With no annotations provided, the description carries full burden for behavioral disclosure. While it mentions the tool is 'useful for finding known exploits' and 'critical for ICS/SCADA security assessments,' it doesn't disclose important behavioral traits like whether this is a read-only operation, potential rate limits, authentication requirements, or what format the results will be in. The description provides context but lacks 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 overly long and poorly structured. While the first two sentences are useful, the extensive lists of examples (ICS/SCADA Exploit Examples, Common ICS CVE Searches) could be condensed or moved to parameter documentation. The description front-loads the purpose but then includes redundant information that doesn't earn its place in the core description.

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 tool's moderate complexity (3 parameters, no output schema, no annotations), the description provides adequate context about purpose and usage scenarios. However, it lacks information about what the tool returns (no output schema) and doesn't fully compensate for the absence of annotations regarding behavioral characteristics. The extensive examples help but don't complete the picture.

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%, so the schema already documents all three parameters thoroughly. The description adds some value by providing extensive examples of query values (especially for ICS/SCADA contexts) and mentioning common facets for ICS, but doesn't add significant semantic meaning beyond what's already in the parameter descriptions. This meets the baseline of 3 when schema coverage is high.

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's purpose as 'Search for exploits in the Shodan Exploits database' with specific verbs ('search', 'finding') and resources ('exploits', 'CVEs', 'software'). It distinguishes from siblings like shodan_host_search or shodan_query_search by focusing specifically on exploits rather than general host or query data.

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 provides clear context for when to use this tool ('Useful for finding known exploits for specific CVEs or software. Critical for ICS/SCADA security assessments') and includes extensive examples of ICS/SCADA-related queries. However, it doesn't explicitly state when NOT to use it or name specific alternative tools among siblings.

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