nmap_scan

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

No annotations are provided, and the description does not disclose any behavioral traits such as potential intrusiveness, network impact, or permission requirements. The agent lacks awareness of whether the scan could trigger alarms or consume significant resources.

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 a single, well-formed sentence that directly states the purpose. It is front-loaded with the action and resource, and every word earns its place without unnecessary detail.

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?

With no output schema, the description should explain what information is returned (e.g., open ports, services, OS detection). It fails to do so. Additionally, it omits context like rate limits or scan duration, making it incomplete for an agent to predict behavior.

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 100% coverage, so parameters are described. However, the description adds no additional meaning beyond the schema—it does not explain the differences between quick, full, and stealth scans or how to specify ports effectively. A baseline of 3 is appropriate since schema covers the basics.

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 the tool performs network scanning with Nmap to discover hosts, ports, and services. It uses a specific verb and resource, and it distinguishes itself from sibling security scanning tools like sqlmap_scan or nikto_scan, which target web applications or databases.

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 no guidance on when to use this tool versus alternatives such as nikto_scan or dirb_scan. It does not mention prerequisites, context, or which scan types are appropriate for different scenarios, leaving the agent without decision-making support.

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