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 what the tool does but doesn't reveal important behavioral traits: whether this is a read-only operation, what permissions are needed, what format the information returns, or potential side effects. The description is functional but lacks transparency about how the tool behaves.

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 extremely concise at just 8 words, front-loading the core purpose and following with a brief usage context. Every word earns its place with no redundancy or unnecessary elaboration. The structure efficiently communicates essential information in minimal space.

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 that an output schema exists (which should document return values), the description's minimal approach is somewhat acceptable. However, for a tool with no annotations and undocumented parameters, the description should provide more context about what accessibility information is retrieved, how it's structured, and typical use cases beyond just 'a11y testing'.

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 schema has 0% description coverage, so the single parameter 'device_serial' is undocumented in the schema. The description provides no information about this parameter - it doesn't explain what device_serial is, when to use it, or what happens when it's null. The description fails to compensate for the schema's lack of parameter documentation.

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 tool's purpose with a specific verb ('Get') and resource ('accessibility service information'), and the 'a11y testing' context adds useful specificity. However, it doesn't explicitly distinguish this from sibling tools like 'toggle_talkback' or 'toggle_high_contrast' which also relate to accessibility features.

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 a11y testing', which suggests when this tool might be appropriate. However, it doesn't offer explicit guidance on when to use this versus alternatives like 'get_device_info' or 'get_app_info', nor does it specify prerequisites or exclusions.

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