bettercap

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

With no annotations provided, the description carries the full burden of disclosing behavior. It does disclose that this is an active attack/Manipulation tool and describes outputs such as captured credentials, session cookies, and traffic logs. However, it omits operational caveats like required privileges, network disruption risks from ARP/DNS spoofing, or the fact that traffic manipulation can have side effects.

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 compact and well-structured: it opens with the core purpose, lists key techniques, states the intended use case, and closes with concrete outputs. Every sentence adds useful information without repetition or filler.

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?

For a tool with all-optional parameters and no output schema, the description provides enough context for correct invocation: what it does, when to use it, and what to expect as output. It lacks details about how caplets/options map to workflows or prerequisites, but the schema fills the parameter gap and the overall context is sufficient.

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 covers all three parameters (opts, iface, caplet) with 100% description coverage, so the baseline is 3. The tool description mentions 'modular caplets' generally but does not add parameter-specific guidance beyond what the schema already provides.

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 identifies bettercap as a real-time MITM attack framework and enumerates specific capabilities (ARP spoofing, DNS spoofing, HTTP/HTTPS manipulation, credential sniffing, session hijacking). This makes its purpose unmistakable and differentiates it from recon/scanning siblings like nmap, tcpdump, or sqlmap.

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?

It explicitly states when to use the tool: 'Use for man-in-the-middle attacks on a local network segment.' It does not explicitly mention exclusions or name alternatives, but the stated context is clear enough for an agent to route toward this tool rather than a scanner or exploit framework.

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