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

With no annotations provided, the description carries the full behavioral burden, and it delivers: it discloses the proxy setup, silent DPC mode versus manual adb mode, CA/proxy installation behavior, fallback conditions, and the certificate-pinning limitation. This gives an agent an accurate model of side effects and failure modes.

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 every sentence earns its place: what it does, how it behaves, what to do next, and when it will fail. The most important action is front-loaded, and technical mode details are packed efficiently without redundancy.

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, this description is complete: it explains the outcome, the two operational modes, prerequisites, limitations, and the next recommended step. An agent has enough context to decide whether to invoke it and what to expect when it does.

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?

The schema already documents the single required parameter 'serial' at 100% coverage, so the description does not need to add much. It reinforces the per-device nature of the operation but does not add new parameter-level meaning beyond the schema baseline.

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 ('Start TLS inspection on an Android device') and explains the concrete mechanism: a per-device TLS-inspecting proxy that decrypts and captures HTTPS traffic. It also distinguishes itself from Chrome DevTools by noting it works for native apps, making it easy to separate from related network-capture tools.

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 gives explicit when-to-use context: use this when you need decrypted HTTPS traffic from native apps, unlike Chrome DevTools. It also names the follow-up tool (android_traffic_flows), explains the two install modes, and states the prerequisite that apps must trust user certificates, with pinned apps called out as not decryptable.

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