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

With no annotations, the description carries the full burden and is largely successful: it discloses network-layer capture, TLS encryption/no HTTP bodies, pcapng output, one-capture-per-device constraint, and auto-stop behavior. It does not explicitly state what happens if a capture is already running, but the constraint is implied.

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?

All four sentences contribute distinct value: purpose, output caveat, optional filters, and workflow/alternative. Front-loaded with the core action and no redundant 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 capture-start tool with no output schema and no annotations, the description covers purpose, output format, filters, lifecycle, and alternatives. It could mention the return/status payload, but it gives enough for an agent to invoke and manage the capture correctly.

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 100%, so the baseline is 3. The description adds value beyond the schema by explaining process and interfaceName filters, giving examples, and tying packets to auto-stop behavior.

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 uses a specific verb and resource: 'Start a device-wide NATIVE network packet capture on an iOS device.' It also names the output format and clearly differentiates from ios_safari_capture_network by contrasting packet-level TLS-encrypted capture with HTTP-body capture.

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?

Provides explicit guidance: use for packet-level Wireshark analysis, pair with ios_pcap_stop, and for Safari HTTP traffic with bodies use ios_safari_capture_network instead. This clearly routes an agent between otherwise similar capture tools.

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