MCP Appium Server

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

With no annotations provided, the description carries full burden for behavioral disclosure. While 'Erase all data' clearly indicates a destructive operation, it doesn't specify whether this is reversible, what types of data are erased (apps, settings, media), whether the simulator remains functional afterward, or any permission requirements. This leaves significant gaps for a tool with clear destructive implications.

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 function with zero wasted words. It's appropriately sized for a simple tool with one parameter and gets straight to the point.

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 tool with no annotations and no output schema, the description is inadequate. It doesn't explain what 'erase all data' entails, what happens to the simulator afterward, whether there are side effects, or what the tool returns. Given the tool's potential impact and lack of structured behavioral information, more context is needed.

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 the single parameter 'udid' well-documented in the schema. The description doesn't add any parameter-specific information beyond what's already in the structured schema, so it meets the baseline expectation without providing extra value.

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 ('Erase all data') and target ('from a simulator'), providing a specific verb+resource combination. However, it doesn't distinguish this tool from other simulator management tools like 'xcode_delete_simulator' or 'xcode_reset_privacy_permission' that might also affect simulator data.

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 about when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., simulator must be booted), exclusions, or relationships to sibling tools like 'xcode_delete_simulator' (which removes the simulator entirely) or 'xcode_reset_privacy_permission' (which resets specific settings).

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