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

Annotations only declare the safety profile (not read-only, not destructive, not idempotent). The description adds real behavioral context the annotations lack: the dual return mechanism (inline base64 under 1 MB vs a .pcapng path written on the RDS host) and the Wireshark follow-up. It still omits failure behavior when no capture is active.

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 short sentences, front-loaded with the action and result, then the two output branches, then a one-line usage tip. Nothing is redundant or padded.

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?

With no output schema, the description correctly carries the return-format burden by explaining the inline-vs-file split. It is nearly complete for a one-parameter stop tool, missing only error/edge behavior (e.g., stopping when no capture is active, whether capture resources are freed).

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% for the single 'udid' parameter, so the schema already does the documentation work. The description adds no parameter-level meaning beyond what is in the schema, which is the expected baseline here.

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 and resource ('Stop the active native packet capture on an iOS device') plus the return artifact ('return the capture as a pcapng'), which cleanly separates it from ios_pcap_start and ios_pcap_status without opening a schema.

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 phrase 'the active ... capture' implies this runs after a capture has been started, but the description never names ios_pcap_start as the prerequisite or says what to do if no capture is running. Usage is inferable but not stated.

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