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

Goes well beyond annotations (which only say non-read-only, non-idempotent, non-destructive): it discloses that it installs a trust profile, that traffic is decrypted, that the default silent path depends on supervision/keybag configuration and falls back to a user-tap prompt, and that certificate-pinned apps will not decrypt. These are exactly the operational caveats an agent needs.

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?

Single front-loaded paragraph that leads with the action and mechanism before caveats; every sentence carries information. It is dense, but the length is justified by the number of caveats (fallback install, pinning, follow-up tool).

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 still tells the agent what the call produces (decrypted HTTPS traffic captured) and how to consume it (ios_traffic_flows). Limitations, defaults, and prerequisites are all covered, so nothing needed to call it correctly is missing.

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% and both parameter descriptions already document udid and the silent/supervision semantics; the description restates the silent default and fallback without adding new syntax or constraints. Baseline 3 is appropriate since the schema carries the parameter detail.

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+resource (start TLS inspection on a physical iOS device) and describes the mechanism (per-device proxy + CA-trust/HTTP-proxy profile). It explicitly distinguishes itself from Safari DevTools and routes the agent to ios_traffic_flows, so it is separable from ios_pcap_start/ios_traffic_stop siblings.

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?

Gives clear sequencing ('Then drive the app and read flows with ios_traffic_flows') and explains the default-vs-fallback install path. It does not explicitly contrast with ios_pcap_start or say when packet capture is preferable to TLS decryption, so it stops short of full when/when-not guidance.

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