websex_network_mapper

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

With no annotations, the description carries the full burden, and it does disclose meaningful behavior: the container executes netdiscover directly with argv tokens and never uses shell parsing, which tells the agent about injection safety and argument handling. It omits privilege/root requirements, expected runtime, and whether the scan is disruptive on the target network.

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?

Three short sentences, front-loaded with what the tool is, followed by the execution model and path convention. No filler, though the mid-sentence execution detail could be tightened.

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?

An output schema exists, so return values need not be described. For a containerized network scanner with zero annotation coverage and an undocumented 4-parameter schema, the description covers the execution model but leaves privilege requirements and operational expectations unspecified.

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 coverage is 0%, so the description must compensate. It partly does: 'arguments' are clarified as argv tokens passed without shell parsing, and 'working_directory' is addressed via the relative-paths guidance. 'stdin' and the engagement namespace binding are never explained.

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?

States a concrete verb (run) plus the specific underlying resource (netdiscover network mapper), which distinguishes it from the other scanners in the namespace (nmap, arp_scan, netbios_scan). It stops short of an explicit contrast with those siblings, but the tool identity is unambiguous.

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?

Naming netdiscover implies the reconnaissance context, and 'use relative paths for engagement artifacts' gives an operational cue. However, there is no explicit when-to-use versus the many sibling scanners (nmap, arp_scan, masscan) and no when-not guidance.

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