MCP Appium Server

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions 'pull a file' but doesn't specify what happens (e.g., copies to local storage, returns file content, requires device access), potential side effects (e.g., file locks), or error conditions (e.g., missing file permissions). This leaves significant gaps for a tool that interacts with device files.

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 no wasted words. It's front-loaded with the core action ('pull a file'), making it easy to scan and understand quickly.

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 interacts with device files (a potentially complex operation), the description is insufficient. With no annotations, no output schema (so return values are undocumented), and minimal behavioral context, it fails to provide enough information for safe and effective use, especially given the many sibling tools in this server.

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 input schema has 100% description coverage, with the 'path' parameter clearly documented as 'Path to the file on the device'. The description doesn't add any extra meaning beyond this, such as path format examples or constraints, but the schema provides adequate baseline information.

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 verb ('pull') and resource ('a file from the device'), making the purpose immediately understandable. However, it doesn't distinguish this tool from its sibling 'push-file', which handles the opposite operation, nor does it specify what 'pull' means in this context (e.g., copy, download, or retrieve).

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. Given the sibling list includes 'push-file' (for sending files to the device) and other file-related tools like 'xcode_copy_to_simulator', there's no indication of prerequisites, context (e.g., device connectivity), or comparisons to similar tools.

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