Android MCP

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

The description adds useful context about what the tool returns (device state, optionally with visual screenshot and annotation controls) beyond the readOnlyHint annotation. However, it doesn't disclose important behavioral traits like whether this requires specific device permissions, what format the state information returns in, or any rate limits. The description doesn't contradict the readOnlyHint annotation.

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 appropriately concise with three sentences that each add value. It's front-loaded with the core purpose, then explains parameter functionality. There's no wasted text, though it could be slightly more structured with clearer separation between purpose and parameter explanations.

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 state retrieval with visual options), no output schema, and minimal annotations, the description is adequate but incomplete. It covers the basic functionality and parameters well, but lacks information about return format, error conditions, or prerequisites. For a tool that presumably returns structured device state data, more context about the response would be helpful.

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?

With 0% schema description coverage, the description carries full burden for parameter documentation. It effectively explains both parameters: 'use_vision' controls whether a visual screenshot is included, and 'use_annotation' controls bounding box display. It even provides default values (True for use_annotation) and clarifies the clean screenshot option when use_annotation=False.

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: 'Get the state of the device' with optional visual screenshot capabilities. It specifies the verb ('Get') and resource ('state of the device'), but doesn't explicitly differentiate from siblings like 'ListDevices' or 'ConnectDevice' which might provide different types of device information.

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. It explains parameter functionality but doesn't mention when this tool is appropriate compared to sibling tools like 'ListDevices' (which might list available devices) or 'ConnectDevice' (which might establish connections).

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