Enhanced ADB MCP Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action ('reset') but doesn't clarify if this requires specific permissions, whether it affects device state permanently, or what happens if the device is disconnected. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence with no wasted words. It's front-loaded with the core action and outcome, making it easy to parse quickly. Every part of the sentence contributes directly to understanding the tool's purpose.

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 an output schema (which handles return values), no annotations, and a simple single optional parameter, the description is minimally adequate. However, as a mutation tool with no behavioral context or usage guidelines, it lacks completeness for safe and effective use by an AI agent, especially compared to siblings like 'change_screen_size'.

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 description doesn't mention parameters, but the input schema has only one optional parameter ('device_serial') with 0% schema description coverage. Since there are zero required parameters, the baseline is high. The description implies the tool operates on a device, which aligns with the parameter, but doesn't add specific details beyond what the schema title ('Device Serial') suggests.

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 ('reset') and target ('screen size') with the specific outcome ('to physical default'). It distinguishes from sibling tools like 'change_screen_size' by focusing on restoration rather than modification. However, it doesn't explicitly contrast with 'reset_density', which is a similar reset operation for a different property.

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 no guidance on when to use this tool versus alternatives like 'change_screen_size' or 'reset_density'. It doesn't mention prerequisites, such as needing a connected device, or scenarios where resetting is appropriate (e.g., after testing different sizes).

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