masscan_scan

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

No annotations are provided, so the description carries the full burden. It discloses that masscan needs root, runs as root in a Kali container, caps rate at 5000 to avoid flooding, and summarizes output structure via OUTPUT_DESCRIPTION. It could further detail potential side effects, but what is provided is transparent about execution requirements and output.

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 well-structured with a one-line summary followed by organized fields (USECASE, INSTRUCTIONS, PREREQUISITES, etc.). There is minor redundancy between the first sentence and USECASE, but overall it is efficient and each section adds value.

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 covers purpose, usage, prerequisites, input descriptions, output format, examples, and related tools. For a network scanning tool, this is quite complete. It lacks some edge-case behaviors (timeouts, error handling), but the essentials are well covered.

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 input schema has zero description coverage, so the description must compensate. The Args section thoroughly explains each parameter: target as host/IP/CIDR, ports with examples (e.g., '1-65535' or '80,443'), and rate with a cap and purpose. This adds significant meaning beyond the raw schema.

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 clearly states 'Run a fast masscan port sweep against an authorized target' and USECASE 'Rapidly identify open TCP ports across an in-scope host or range', which fully captures the tool's function. It is also distinct from siblings like nmap_scan (detailed scan) and host_discovery due to the 'fast' and 'port sweep' emphasis.

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?

The description provides prerequisites (target authorization, root requirement) and lists related tools (nmap_scan, host_discovery), but does not explicitly say when to use this tool versus alternatives. The USECASE implies a particular scenario, but exclusions or direct comparisons are missing.

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