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

The annotations declare this is a non-read-only, non-idempotent, non-destructive write, and the description adds substantial behavior beyond that: the two install modes (dpc vs manual), that the Device Owner path installs the proxy AND CA silently with zero on-device interaction, the fallback to an adb global proxy, and the cert-pinning limitation. This is unusually rich disclosure for a mutation tool.

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 action is front-loaded in the first clause and every sentence carries information (mechanism, install modes, prerequisites, follow-up tool, limitation). It is dense and parenthesis-heavy with mode labels and path names, which is slightly taxing but not wasteful.

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 mutation tool with no output schema, the description covers mechanism, both execution paths, prerequisites, the natural next tool, and the failure mode (pinned apps). Nothing an agent needs 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?

There is a single parameter (serial) with 100% schema description coverage, so the schema already documents it fully. The description frames the operation as per-device but adds no format or syntax detail for the serial beyond what the schema provides, so the baseline of 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?

States a specific verb (start TLS inspection) and resource (Android device traffic) and describes the concrete mechanism: bringing up a per-device TLS-inspecting proxy and pointing the device at it. It explicitly distinguishes itself from Chrome DevTools and names the companion read tool android_traffic_flows, so an agent can place it against siblings without opening a 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?

Gives clear when-to-use context (native app HTTPS capture, which DevTools cannot do), the prerequisite that the app must already trust user certificates, and the follow-up step (drive the app and read flows with android_traffic_flows). It also states the exclusion that certificate-pinned apps will not decrypt, which is exactly the kind of routing information an agent needs.

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