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. While 'Uninstall' implies a destructive operation, the description doesn't disclose important behavioral aspects: whether this requires specific permissions, if the operation is reversible, what happens if the app isn't installed, or what the response looks like (success/failure indicators).

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 that directly states the tool's purpose with zero wasted words. It's appropriately sized for a straightforward tool and front-loads the essential information.

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 destructive operation tool with no annotations and no output schema, the description is inadequate. It doesn't explain what happens after uninstallation, potential side effects, error conditions, or how this tool differs from the sibling 'uninstall-app' tool. The context signals show this is part of an Xcode simulator management suite, but the description doesn't leverage this 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?

Schema description coverage is 100%, with both parameters (udid, bundleId) clearly documented in the schema. The description adds no additional parameter information beyond what's already in the structured schema. This meets the baseline of 3 when schema coverage is complete.

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 ('Uninstall') and target ('an app from a simulator'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from the sibling 'uninstall-app' tool, which appears to serve a similar purpose but potentially for different contexts (e.g., physical devices vs simulators).

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. There's no mention of prerequisites (e.g., simulator must be booted), comparison with the sibling 'uninstall-app' tool, or any context about when this Xcode-specific tool is preferred over general appium tools.

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