MCP Appium Server

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

No annotations are provided, so the description carries full burden. It mentions 'without focusing on any element', which hints at a behavioral trait (bypassing UI focus), but doesn't disclose critical details like whether this requires device unlock, what happens if the device is locked, whether it's safe for automation, or if there are rate limits. For a tool that sends input to a device with zero annotation coverage, this is insufficient.

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 waste. It's front-loaded with the core action and includes a key behavioral note ('without focusing on any element'). Every word earns its place, making it appropriately sized for a simple tool.

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 complexity (device interaction tool with potential side effects), no annotations, no output schema, and minimal description, this is incomplete. The description doesn't cover what the tool returns, error conditions, or important behavioral constraints. For a tool that could affect device state, more context is needed to use it safely and effectively.

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 description coverage is 100% with one parameter ('text'), and the description doesn't add any parameter-specific information beyond what's in the schema. The baseline is 3 when the schema does the heavy lifting, but the description could have clarified what 'text' means in this context (e.g., raw keyboard input vs. commands).

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 states the tool 'Send keys directly to the device without focusing on any element', which provides a clear verb ('send keys') and resource ('device'), but it's somewhat vague about what 'keys' means (text input vs. keyboard keys) and doesn't distinguish from sibling tools like 'send-keys' or 'send-key-event'. It's not tautological but lacks specificity compared to other device interaction tools.

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 minimal guidance: it mentions 'without focusing on any element', which implies this is for raw input rather than element-specific interaction. However, it doesn't explain when to use this versus alternatives like 'send-keys' (which might require element focus) or 'send-key-event' (which might send hardware key codes). No explicit when/when-not rules or prerequisite context is provided.

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