iOS Simulator MCP

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

Annotations indicate readOnlyHint=false (implying mutation) and openWorldHint=true (suggesting flexible use), but the description adds minimal behavioral context. It confirms this is an input action for iOS Simulator, which aligns with annotations, but doesn't elaborate on effects (e.g., text entry in UI), rate limits, or error conditions, offering only basic value beyond annotations.

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, direct sentence with zero wasted words, efficiently conveying the core action. It's appropriately sized for a simple tool and front-loaded with essential information, making it highly concise and well-structured.

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?

Given the tool's moderate complexity (UI interaction with mutation), annotations cover safety (readOnlyHint=false) and flexibility (openWorldHint=true), but no output schema exists. The description is minimal, lacking details on return values, error handling, or integration with sibling tools, making it adequate but with clear gaps for an interactive tool.

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 clear parameter descriptions in the schema (udid for target identification, text for input). The description doesn't add any meaning beyond this, such as explaining parameter interactions or usage examples, so it meets the baseline for high schema coverage without compensation.

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 ('Input text') and target ('iOS Simulator'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like ui_tap or ui_swipe, which are also UI interaction tools for the simulator, so it lacks sibling distinction.

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. It doesn't mention prerequisites (e.g., needing a booted simulator), exclusions, or comparisons to sibling tools like ui_tap for different interactions, leaving the agent to infer usage context.

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