Enhanced ADB MCP Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the tool sets a proxy for debugging, implying a configuration change, but doesn't specify whether this requires device permissions, affects other network operations, is persistent across reboots, or has side effects. For a mutation tool with zero annotation coverage, this leaves significant behavioral gaps unaddressed.

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 efficiently structured in a single sentence with zero wasted words. It front-loads the core purpose ('Set HTTP proxy for the device') followed by a brief usage note ('useful for debugging network requests'). Every element earns its place without redundancy or unnecessary elaboration.

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's moderate complexity (device configuration change), no annotations, and an output schema (which reduces need to describe returns), the description is minimally adequate. It covers the basic purpose and hints at usage context but lacks details on parameters, behavioral implications, and alternatives. The presence of an output schema prevents a lower score, but significant gaps remain.

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 0%, so the description must compensate for parameter documentation. It mentions 'HTTP proxy' which relates to 'host' and 'port', but doesn't explain parameter semantics (e.g., host format, port range, optional 'device_serial' for multi-device contexts). With 3 parameters entirely undocumented in schema, the description adds minimal value beyond the tool name.

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 action ('Set HTTP proxy') and resource ('for the device'), making the purpose immediately understandable. It distinguishes from sibling tools like 'clear_proxy' by specifying a setting action rather than clearing. However, it doesn't explicitly differentiate from other network-related tools like 'get_network_info' or 'toggle_wifi' beyond the proxy-specific focus.

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 provides implied usage context with 'useful for debugging network requests', suggesting this tool is for diagnostic purposes. However, it lacks explicit guidance on when to use this versus alternatives (e.g., 'clear_proxy' for removing proxy settings) or prerequisites (e.g., device connectivity requirements). The context is helpful but incomplete for optimal agent decision-making.

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