tap-by-ios-class-chain

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

With no annotations provided, the description carries full burden but offers minimal behavioral context. It mentions the action (tap) but doesn't disclose what happens on failure (timeout behavior), whether it waits for element visibility, if it scrolls to find elements, error conditions, or performance characteristics. The description is technically accurate but lacks operational details.

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 extremely concise - a single sentence that communicates the core functionality efficiently. Every word earns its place: 'Tap' (action), 'on an element' (target), 'using iOS class chain' (method), and 'iOS only' (platform constraint). No wasted words or redundant 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 an interactive UI automation tool with no annotations and no output schema, the description is insufficient. It doesn't cover success/failure behavior, error handling, platform version requirements, element state prerequisites, or what constitutes a valid tap. Given the complexity of mobile automation and the many sibling tools with overlapping functionality, 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?

Schema description coverage is 100%, providing clear documentation for both parameters. The description doesn't add any parameter semantics beyond what's in the schema - it mentions 'iOS class chain' which aligns with the classChain parameter but provides no additional context about format, validation, or usage examples beyond the schema's example.

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 an element') and the method ('using iOS class chain'), with the platform constraint ('iOS only') explicitly mentioned. It distinguishes from general tap tools by specifying the iOS class chain method, though it doesn't explicitly differentiate from its closest sibling 'tap-by-ios-predicate' which uses a different iOS locator strategy.

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 minimal guidance - only that it's for iOS. It doesn't indicate when to use this versus alternatives like 'tap-by-ios-predicate', 'tap-element', or 'smart-tap', nor does it mention prerequisites like needing an active iOS session or element visibility requirements.

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