websex_masscan

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

With no annotations, the description carries the full behavioral burden. It usefully discloses that masscan is executed directly with argv tokens and that shell parsing is never used, plus namespace and path behavior. However, it omits safety profile, rate limits, destructive potential, and authorization requirements for a network scanner.

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 concise sentences, front-loaded with the core action and followed by essential execution context. No wasted words; every sentence adds relevant information.

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 need not be described. Yet with no annotations and 0% schema description coverage, the description should explain more about stdin, working_directory defaults, argument structure, and when to select masscan versus other scanners. It is adequate but incomplete.

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 0%, so the description must compensate. It hints that 'arguments' are argv tokens and that 'engagement_id' selects the namespace, and 'relative paths' relates to working_directory. But it does not explain stdin, the array-of-strings format, or the default working directory.

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?

States a specific verb and resource: 'Run masscan from the WebSex network toolkit.' An agent can tell it runs masscan, but the description does not differentiate it from sibling network scanners such as websex_nmap or websex_rustscan.

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?

Provides execution constraints ('Runs from the selected engagement namespace; use relative paths for engagement artifacts') but no guidance on when to choose masscan over alternatives like nmap or rustscan. There are no when-to-use or when-not conditions.

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