masscan

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states 'Fast port scanner' and does not mention whether the scan is intrusive, requires permissions, affects the target, or what outputs are generated. This lack of transparency could lead to unexpected behavior.

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 concise (one sentence), but it is underspecified. It does not earn its place because it omits critical context needed for correct tool selection and use. Conciseness without completeness reduces utility.

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 tool has 4 parameters, no output schema, and no annotations, the description is severely incomplete. It fails to explain return values, required permissions, or behavior beyond scanning. The agent lacks sufficient information to use the tool correctly or interpret results.

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 only 25% (dry_run has a description). The tool description adds no additional meaning to parameters like 'target', 'ports', or 'session_id'. For a low-coverage schema, the description should compensate but fails to do so, leaving parameter semantics vague.

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 'Fast port scanner' clearly states the tool's function (port scanning) and a key attribute (speed). However, it does not distinguish masscan from sibling tools like nmap, which also performs port scans. The purpose is clear but lacks specificity to differentiate it in a list of similar tools.

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 usage guidelines are provided. The description does not indicate when to use masscan over alternatives such as nmap or other scanners. There is no mention of preferred scenarios, prerequisites, or exclusions, leaving the agent without decision support.

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