websex_packet_capture

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

No annotations are provided, so the description must carry the full burden. It helpfully discloses that tcpdump is executed directly with argv with no shell parsing (important for security and quoting), and that it runs from the engagement namespace. However, it does not disclose required privileges (CAP_NET_RAW/root) or that captures may be written to disk and where.

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 tight sentences, front-loading what the tool does. It is appropriately sized but could more clearly separate the intended use from the tcpdump execution 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?

Given four undocumented parameters, no annotations, and a mutation-ish operation that may require elevated privileges, the description is only partially complete. It covers how commands are executed but misses prerequisites, capture output location, and parameter semantics.

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 must compensate. It only adds indirect guidance that argv tokens are passed to tcpdump and that relative paths are for engagement artifacts, but does not explain engagement_id, stdin, working_directory, or the expected format of the arguments array beyond raw tcpdump flags.

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 specific verb (run packet capture) and the underlying tool (tcpdump) with supplied argv tokens. Clearly distinguishes from siblings like websex_packet_analysis or websex_nmap by being a raw capture primitive.

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 implies use within a WebSex engagement namespace and for relative artifact paths, but does not state when to use this over websex_packet_analysis or websex_bash. No explicit alternatives or exclusions are provided.

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