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

With no annotations provided, the description carries the full burden, and it covers the key behavioral traits: starting a per-device TLS-inspecting proxy, installing a CA-trust and HTTP-proxy profile, defaulting to silent supervised install, falling back to an interactive prompt when unsupervised, and warning about certificate-pinned apps.

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?

The description is dense but well-structured: main purpose is front-loaded, followed by mechanism, usage guidance, fallback behavior, and a limitation. Every sentence earns its place, with no 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 2-parameter tool with no output schema and no annotations, the description is complete enough for an agent to invoke it correctly. It explains what will happen on the device, the silent/prompt decision, the limitation with pinned apps, and points to the follow-up tool for reading captured flows.

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, but the description adds meaningful semantics beyond the schema: it explains the silent parameter's default, the supervision keybag prerequisite, and the fallback to a prompt install. It does not need to explain udid further, as 'iOS device UDID' is self-explanatory.

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 opens with 'Start TLS inspection on a physical iOS device', giving a specific verb and resource. It details what happens (proxy + CA-trust/HTTP-proxy profile, HTTPS decryption) and explicitly contrasts with Safari DevTools for native apps, making it easy to distinguish from ios_traffic_flows and ios_traffic_status.

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?

It states when this tool is appropriate: inspecting HTTPS traffic on a physical iOS device, especially for native apps where Safari DevTools falls short. It also gives an explicit exclusion ('Certificate-pinned apps will not decrypt') and directs the agent to the next step ('read flows with ios_traffic_flows').

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