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. 'Enable or disable' implies a state change operation, but there's no information about permissions required, whether changes persist across reboots, what happens on different Android versions, or error conditions. The description is minimal and doesn't provide meaningful behavioral context beyond the basic action.

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 zero wasted words. It's appropriately sized for a simple toggle operation and front-loads the essential action. Every word earns its place.

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 this is a state mutation tool with no annotations, 0% schema description coverage, and multiple similar sibling tools, the description is inadequate. It doesn't explain what high contrast text affects, whether it requires specific Android settings or permissions, what the output contains (though output schema exists), or how it differs from other accessibility toggles. The presence of an output schema helps but doesn't compensate for the missing behavioral context.

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 but doesn't mention parameters at all. The schema shows 'enable' (boolean) and 'device_serial' (optional string), but the description provides no context about what 'enable' actually does, when device_serial is needed, or how these parameters interact. Baseline is 3 since schema coverage is low but description adds no parameter information.

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 verb ('enable or disable') and resource ('high contrast text'), making the purpose immediately understandable. However, it doesn't distinguish this from sibling tools like 'toggle_color_inversion' or 'toggle_show_layout_bounds' which are also accessibility toggles, preventing a perfect score.

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, prerequisites, or context. With multiple toggle tools in the sibling list (color_inversion, show_layout_bounds, show_taps, talkback), there's no indication of when high contrast text is appropriate versus other accessibility features.

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