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

Annotations only declare the safety hints; the description goes well beyond them by disclosing the ref-counted shutdown model, the stillRunning: true response field (especially valuable with no output schema), and exactly what cleanup entails (profile removed, proxy killed, buffered flows discarded). The 'buffered flows discarded' detail sits in mild tension with destructiveHint=false, but this is the tool's own transient capture buffer, not user resource destruction, so it is not a contradiction.

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 front-loaded sentences with no filler: scope first, concurrent-consumer behavior second, full-teardown condition third. Each sentence adds a distinct operational fact; nothing is restated from the schema or annotations.

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 one-parameter, no-output-schema tool, it covers everything an agent needs: what is stopped, what remains running for other consumers, the stillRunning response signal, and when full teardown occurs. No meaningful gap remains.

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?

There is a single udid parameter at 100% schema description coverage, so the schema already carries its meaning. The description adds no format or syntax detail for udid beyond the schema, and the 'consumer only' semantics describe the caller rather than the parameter, so baseline 3 applies.

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 and resource ('Stop TLS inspection for a device') and immediately scopes it to 'THIS (AI) consumer only', which distinguishes it from capture-management siblings like ios_traffic_start and ios_traffic_status without opening their schemas.

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 gives a clear condition for the tool's effect: call it to release this consumer's capture, and note that other consumers (workspace UI or another agent) keep the proxy/profile alive. It does not explicitly name a sibling alternative to use instead, but the when-to-use context is unambiguous.

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