masscan

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

With no annotations, the description should disclose behavioral traits. It only mentions speed, but omits details like rate limiting, permissions required (e.g., root), or potential for disruption. Minimal transparency.

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 very short (3 words) but not necessarily concise in a useful way. It lacks crucial details that could be added without significant length. Front-loading is minimal.

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 no annotations, no output schema, and low schema coverage, the description is severely incomplete. An agent cannot determine correct usage, required permissions, or how to interpret results among 25+ sibling tools.

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%, and the description adds no parameter information. It does not explain the format of 'target' (IP vs domain), the purpose of 'session_id', or how to specify 'ports' (e.g., range syntax).

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 indicates the tool performs port scanning, which is a specific verb and resource. However, it does not differentiate from sibling tools like nmap or quick_scan, which also scan ports.

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 masscan vs alternatives. The description lacks context about scenarios where masscan's speed is beneficial or trade-offs compared to nmap.

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