websex_shodan

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

With no annotations, the description carries the full burden; it usefully discloses that argv tokens are passed directly with no shell parsing and that execution is scoped to an engagement namespace. However, it omits critical behavior for a shodan client: the required API key/auth, network egress implications, and any rate limits or read-only nature.

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?

Three sentences, front-loaded with the core purpose followed by behavioral and path-scoping details; minimal waste. No redundancy with the schema, though it could be tightened slightly.

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?

An output schema exists so return values needn't be explained, and the invocation mechanics are covered. But for a 4-param, unannotated CLI wrapper, the missing stdin parameter documentation and absent authentication/egress requirements leave meaningful gaps.

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 implicitly covers three params by naming 'argv tokens' (arguments), the engagement namespace (engagement_id), and relative artifact paths (working_directory), but it never mentions the 'stdin' parameter and gives no format details for any of them.

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 states a specific verb and resource ('Run shodan from the WebSex enumeration toolkit'), making clear it wraps the shodan CLI. It does not explicitly differentiate from similar sibling recon tools such as websex_censys or websex_amass, so it falls short of a 5.

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 gives operational context ('Runs from the selected engagement namespace; use relative paths for engagement artifacts') but never says when to choose this tool over alternatives like censys or the harvester. Usage is implied rather than stated.

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