MCP Appium Server

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'Install' implies a write/mutation operation, the description doesn't mention permission requirements, whether the installation is reversible, potential side effects, or what happens if installation fails. For a tool that modifies device state, this is a significant gap in behavioral transparency.

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 5 words, front-loading the essential information with zero wasted words. Every word earns its place by specifying the action, target, and platform. The structure is optimal for quick comprehension.

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?

For a tool that performs device modification (installing applications) with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after installation, whether verification occurs, what errors might be returned, or how to handle installation failures. Given the complexity of device operations and the lack of structured metadata, the description should provide more complete 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?

With 100% schema description coverage, both parameters are already documented in the schema. The description doesn't add any additional semantic context about the parameters beyond what's in the schema descriptions. It doesn't explain APK file format requirements, device connectivity prerequisites, or installation behavior details. The baseline of 3 is appropriate given the schema does the parameter documentation work.

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 action ('Install') and resource ('Android application APK'), making the purpose immediately understandable. It doesn't specifically differentiate from sibling tools like 'xcode_install_app' or 'uninstall-app', but the Android focus provides some distinction. The description avoids tautology by specifying what's being installed.

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. With sibling tools like 'xcode_install_app' (for iOS) and 'uninstall-app' (for removal), there's no indication of when this Android-specific installation tool is appropriate versus other installation methods. No prerequisites or contextual usage information is provided.

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