iOS Simulator MCP

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

Annotations indicate this is not read-only and has open world characteristics. The description adds the specific behavioral context of tapping on an iOS Simulator screen, which goes beyond the annotations. However, it doesn't mention important behavioral details like whether this requires a running simulator, what happens if coordinates are out of bounds, or error conditions.

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 states the core functionality without any wasted words. It's appropriately sized for a straightforward UI interaction tool and gets directly 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 tool with 4 parameters, no output schema, and annotations covering basic safety/scope, the description is minimally adequate. It states what the tool does but lacks important context about when and how to use it effectively, especially given the sibling tools available for similar UI interactions.

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?

With 100% schema description coverage, the schema already documents all parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain coordinate systems, duration units, or UDID usage context. The baseline of 3 is appropriate when the schema does the heavy lifting.

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 ('Tap on the screen') and target ('iOS Simulator'), providing a specific verb+resource combination. However, it doesn't distinguish this from sibling tools like 'ui_swipe' or 'ui_describe_point' which also interact with the iOS Simulator UI.

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 (like needing a booted simulator), comparison to similar UI interaction tools, or specific use cases where tapping is appropriate versus other actions.

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