Intercept Android Device via ADB

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

With no annotations provided, the description carries the full burden. It discloses key behavioral traits: it intercepts HTTP(S) traffic, automatically injects HTTPS certificates for rooted devices and most emulators, and implies it requires ADB connectivity. However, it lacks details on permissions, rate limits, or what happens during interception.

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 front-loaded with the core purpose in the first sentence, followed by a key capability in the second. Both sentences earn their place by providing essential information without redundancy or unnecessary details.

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?

Given no annotations and no output schema, the description is moderately complete. It covers the tool's purpose and a key behavioral trait (certificate injection), but lacks details on prerequisites (e.g., ADB setup), error handling, or return values, which are important for a tool with 3 parameters and potential complexity.

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 description coverage is 100%, so the schema already documents all parameters. The description does not add any meaning beyond what the schema provides, such as explaining how 'proxyPort' relates to traffic routing or 'deviceId' selection. Baseline 3 is appropriate given high schema coverage.

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 clearly states the specific action ('Intercept HTTP(S) traffic') and resource ('Android device or emulator connected via ADB'), distinguishing it from sibling tools like 'intercept_chrome' or 'frida_android_intercept' by specifying the ADB-based Android interception method.

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?

No explicit guidance is provided on when to use this tool versus alternatives like 'frida_android_intercept' or 'intercept_chrome'. The description mentions automatic certificate injection for rooted devices and emulators, but this is a capability statement rather than usage guidance.

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