kali_network_tcpdump_capture

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

No annotations are provided, so the description carries full burden. It mentions behavioral aspects like supporting BPF filters and saving to PCAP files, but lacks critical details: it doesn't state if this requires elevated privileges (e.g., root), whether it's destructive or read-only, potential performance impacts, or output format beyond file saving. For a network capture tool with zero annotation coverage, this is insufficient.

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, efficient sentence with zero waste. It's front-loaded with the core purpose and includes only essential additional capabilities. Every word earns its place, making it easy to parse quickly.

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 tool's complexity (network packet capture with 6 parameters) and lack of annotations/output schema, the description is moderately complete. It covers the high-level purpose and key features but misses critical behavioral context (e.g., permissions, side effects). With no output schema, it also doesn't describe return values, leaving gaps for agent usage.

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 100%, so parameters are well-documented in the schema. The description adds minimal value beyond the schema—it mentions BPF filters and PCAP files, which relate to the 'filter' and 'output_file' parameters but don't provide additional semantics. Baseline 3 is appropriate when the schema does the heavy lifting.

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's purpose: 'Capture network packets for analysis.' It specifies the action (capture) and resource (network packets), and mentions key capabilities (BPF filters, PCAP file saving). However, it doesn't explicitly differentiate from its sibling 'kali_network_tshark_capture', which likely serves a similar packet capture function.

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. It doesn't mention sibling tools like 'kali_network_tshark_capture' for comparison, nor does it specify prerequisites, contexts, or exclusions for usage. The agent must infer usage from the tool name and description alone.

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