nmap_ping_scan

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

With no annotations, the description must carry the burden of behavioral disclosure. It informs that this is a ping-only scan, but does not mention potential permission requirements, scope limitations, or that it only identifies live hosts without port information.

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?

A single sentence that efficiently conveys the core function. It is front-loaded with key information, but lacks any additional structure (e.g., bullet points or sections) that could improve readability.

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 presence of an output schema (not shown), the description may not need to detail return values. However, it provides no context about expected output, behavior on failure, or integration with other nmap tools, making it moderately complete.

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 should explain parameters. It does not mention what target or timeout mean beyond their names and defaults. The target's default suggests a subnet format, but no explicit format or range guidance is given.

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?

Description clearly states the tool performs a ping scan using -sn to discover online hosts in a LAN. This is specific enough to understand its purpose, though it does not explicitly distinguish from similar siblings like nmap_quick_scan or nmap_comprehensive.

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 this tool versus alternatives such as nmap_comprehensive or nmap_service_scan. The description does not mention limitations, prerequisites, or typical use cases.

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