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 states the tool waits for readiness but doesn't explain what 'ready' means (e.g., booted, responsive), whether it blocks execution, what happens on timeout, or if it requires specific permissions. This leaves significant gaps for a tool that likely interacts with system resources.

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 wasted words. It's front-loaded with the core purpose, making it easy to parse 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 with no annotations and no output schema, the description is incomplete. It lacks details on behavioral traits (e.g., blocking nature, error handling), expected outcomes, or how it fits into broader workflows with sibling tools, making it inadequate for safe and effective use.

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%, so the schema fully documents both parameters (udid and timeoutMs). The description doesn't add any meaning beyond what's in the schema (e.g., it doesn't clarify UDID format or typical timeout values), resulting in a baseline score of 3.

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 'Wait for a simulator to be ready' clearly states the action (wait) and resource (simulator), making the purpose understandable. However, it doesn't differentiate from sibling tools like 'xcode_get_simulator_status' or 'xcode_boot_simulator', which might have overlapping functions related to simulator readiness.

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 on when to use this tool versus alternatives. The description doesn't mention prerequisites (e.g., whether the simulator must be booted first), exclusions, or how it relates to siblings like 'xcode_boot_simulator' or 'xcode_get_simulator_status'.

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