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

Goes well beyond the annotations, which only say readOnlyHint=false, idempotentHint=false, destructiveHint=false. The description discloses consumer-scoped reference counting, the stillRunning: true response signal, and exactly what is destroyed when the last consumer stops (proxy killed, device proxy/CA cleared, buffered flows discarded).

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 sentences, front-loaded with the action and its scope, then the non-obvious conditional behavior. Dense but essentially waste-free; the final sentence is long yet each clause (killed proxy, cleared CA, discarded flows) carries distinct information.

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?

No output schema exists, and the description pre-emptively covers the key return signal (stillRunning: true). Given a single fully-documented parameter and the teardown semantics explained, nothing needed to invoke or interpret this call 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 the single 'serial' parameter is fully documented as the adb serial. The description adds no format detail or constraints beyond 'for an Android device', so the schema does the work — baseline 3 is correct for a fully-specified single parameter.

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 TLS inspection for an Android device') plus a precise scope qualifier ('from THIS (AI) consumer only'). An agent can distinguish it from android_traffic_start and ios_traffic_stop without opening any 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?

Explains the condition under which stopping actually tears down proxies ('Only when every consumer has stopped') versus when resources are left running for other consumers. It does not name the counterpart tool (android_traffic_start) or state prerequisites, so it stops short of explicit alternative routing.

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