Set device proxy

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

With no annotations provided, the description must fully disclose behavioral traits. It only states 'Route device traffic' without mentioning that the proxy setting modifies system settings, persists until cleared, or requires an active ADB connection. The agent is left unaware of side effects or dependencies.

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 a single, front-loaded sentence with no wasted words. However, it could earn its place by including more essential context without becoming verbose.

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 the tool has two parameters, no output schema, and no annotations, the description is inadequate. It omits prerequisites (ADB connection), how to handle multiple devices (serial), and what the tool returns or affects. A complete description would address these gaps.

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 50%, and the tool description adds no extra meaning beyond the hostPort parameter's schema description. The serial parameter is undocumented in both schema and description, leaving its purpose unclear. The description fails to compensate for the schema's gaps.

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 uses a specific verb ('Route') and resource ('device traffic through host:port via adb'), clearly stating the tool's function. It distinguishes from siblings like adb_clear_proxy by focusing on setting the proxy, making the purpose unambiguous.

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 on when to use this tool versus alternatives. The mention of 'no WiFi UI needed' hints at a use case but does not specify prerequisites, when to avoid, or suggest sibling tools like adb_clear_proxy for reversal.

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