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

With no annotations provided, the description carries the full burden and does well: it discloses that flows are decrypted, bodies are truncated, only the most recent `limit` flows are returned, and filters are available. It could add explicit behavior when capture is not active, but the core behavioral surface is clearly described.

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?

Five brief, front-loaded sentences cover purpose, returned fields, body inclusion, filtering, and ordering with no filler. Every sentence earns its place and the most important information appears first.

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 no annotations, the description is quite complete: it explains what is returned, when it applies, how to include bodies, and how to filter. The only notable gap is lack of explicit failure/error behavior if traffic capture is not active.

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 baseline is 3. The description restates includeBodies, urlSubstring, onlyErrors, and limit, but does not materially add semantics beyond what the input schema already provides.

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 states a specific verb ('Snapshot') and a precise resource ('recent DECRYPTED HTTPS flows') with clear scope ('captured since ios_traffic_start'). It distinguishes itself from raw-pcap or Android counterparts by emphasizing decrypted HTTPS flow data and listing the returned fields.

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 the prerequisite that traffic capture must have been started via ios_traffic_start and mentions filter options. However, it does not explicitly say when to use this tool over siblings like ios_safari_capture_network or ios_pcap_start, nor does it state 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.