shodan_list_scans

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

The description says 'List', implying a read-only operation, but the annotations declare readOnlyHint=false, which indicates the tool may not be read-only. This is a direct contradiction. Additionally, no other behavioral traits are disclosed.

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, focused sentence: 'List all active on-demand scans.' It is front-loaded, every word contributes, and there is no redundant or filler content.

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 is adequate for a simple list operation with no parameters, but it lacks context about response structure or pagination. The contradiction with annotations further reduces its completeness, leaving the agent uncertain about the tool's behavior.

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?

The tool has zero parameters, and the input schema is empty. As per the baseline for zero-parameter tools, the description does not need to provide parameter details. The description adds no extra parameter semantics because none exist.

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 uses a specific verb ('List') and a clear resource ('active on-demand scans'), making its function unambiguous. It distinguishes itself from sibling tools like shodan_scan_status by focusing on listing all active scans rather than checking an individual scan's status.

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. It lacks any mention of scenarios, exclusions, or comparisons to sibling tools such as shodan_scan_status or shodan_scan.

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