adb_tcpdump_start

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

With no annotations, the description provides key behavioral traits: it requires root and runs in background. However, it does not disclose potential impact on device performance, how to stop the capture, or where the output file is stored. Missing details about file location and retrieval reduce transparency.

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?

Description is very concise at two sentences (18 words), front-loading the primary action and requirements. It avoids unnecessary detail, though it could be slightly more structured (e.g., listing prerequisites). Overall effective and efficient.

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 no output schema and moderate complexity, the description omits crucial context: where captured packets are saved, how to retrieve the file, and that stopping requires the sibling tool. An agent would need this information to use the tool effectively. Completeness is insufficient.

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 the schema already documents all four parameters. The description adds no additional parameter information beyond what the schema provides. Baseline 3 is appropriate as the description does not enhance parameter understanding.

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 'Start a packet capture on the device using tcpdump.' It specifies the action (start), the tool (tcpdump), and the resource (device). Sibling tool 'adb_tcpdump_stop' reinforces the pairing, making the purpose distinct from other ADB tools.

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?

Description mentions prerequisite ('Requires root or tcpdump binary on device') and behavior ('Capture runs in background'), but does not explicitly state when to use this tool versus alternatives like adb_logcat_start or adb_screenrecord_start. There is no guidance on when not to use it.

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