Android MCP

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

Annotations provide destructiveHint=true, indicating a mutation. The description adds minimal behavioral context beyond this, as it doesn't explain what 'Swipe' entails (e.g., screen interaction, potential side effects). However, it doesn't contradict annotations, so it meets a low bar by not misleading, but adds little value.

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, brief sentence, making it front-loaded and efficient. However, the typo ('cordinate') slightly detracts from clarity. Overall, it's appropriately sized with no wasted words, though it could be more precise.

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 complexity (a destructive action with 4 parameters), lack of output schema, and 0% schema coverage, the description is inadequate. It doesn't cover parameter meanings, expected behavior, or context, leaving significant gaps for the agent to infer usage.

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. It mentions 'specific cordinate' but doesn't explain the four parameters (x1, y1, x2, y2) or their roles (e.g., start and end points). This leaves parameters undocumented, failing to add meaningful semantics beyond the bare schema.

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 'Swipe on a specific cordinate' states a verb ('Swipe') and resource ('cordinate'), but it's vague about the context (e.g., mobile device screen) and contains a typo ('cordinate'). It doesn't distinguish from siblings like 'Drag' or 'Click', which reduces clarity. The purpose is understandable but lacks specificity.

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?

No guidance is provided on when to use this tool versus alternatives such as 'Drag' or 'LongClick'. The description implies usage for swiping but offers no context about prerequisites, device state, or exclusions. This leaves the agent without clear direction for tool selection.

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