shodan_internetdb_zero_key_ip_port_cve_scanner

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

No annotations are provided, so the description carries the full burden, yet it discloses almost nothing: not that the feed is zero-key/keyless (only implied in the name), nothing about rate limits, caching, or data staleness, and nothing about what the extracted structured items contain. For a data-extraction feed with no annotation coverage, this leaves the agent guessing about cost, auth, and failure modes.

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?

It is short, but the length comes from duplication rather than economy: the name is repeated verbatim before and after the colon, and "Real-time structured data extraction feed" is marketing filler. No sentence adds information the name did not already carry.

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?

With no annotations, no output schema, and only one parameter, the description is the sole source of behavioral and usage context, and it supplies none of it. It also fails to resolve how an IP target is specified, which is the single most important ambiguity for this tool.

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 100% for the single optional maxResults parameter, so the baseline of 3 applies; the description adds no meaning beyond the schema. Notably it never clarifies how the target IP is supplied, which is a real ambiguity given the tool is nominally an IP scanner with no IP parameter.

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 is a tautology: it restates the tool name twice ("Shodan InternetDB IP Open Ports, CPE & CVE Scanner") without ever stating in plain terms what an invocation does or returns. Whatever specificity exists comes from the name itself, not the description, so the agent gets no independent confirmation of the tool's function.

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?

There is no when-to-use guidance, no exclusions, and no routing to alternatives such as cloud_perimeter_ip_attack_surface_auditor or ot_ics_scada_exposed_port_vulnerability_radar, which plausibly overlap. The only contextual hint is the word "Real-time," which describes data freshness rather than when to select this tool.

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