shodan_scan_internet

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

Annotations are absent; description carries full burden. It only says 'Scan the internet' without disclosing behavioral traits such as destructive potential, authorization needs, or side effects like API credit consumption or scan duration.

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?

Extremely short (one sentence) but underspecified. It lacks essential context, making it incomplete rather than concise.

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 complexity of internet scanning and the presence of an output schema (not shown), the description is insufficient. It does not explain scope, return format, or how it differs from other scanning tools. Without annotations, more detail is needed.

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% with descriptions for both parameters (port, protocol). Description adds no extra meaning beyond schema. Baseline 3 applies.

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?

Description states 'Scan the internet using Shodan', which gives a broad purpose. However, it does not differentiate from siblings like shodan_scan (which likely scans a specific IP/range) or shodan_host. The verb 'scan' and resource 'internet' are clear but vague.

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 on when to use this tool vs alternatives. No mention of prerequisites, rate limits, or appropriate contexts. The agent is left to infer usage from the name alone.

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