Smart Tap (AI) [Pro]

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

Correctly describes the tool's behavior (finds element, taps its center) and return value (success flag and element tapped). With no annotations, it carries the full burden and does so well.

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?

Three sentences covering purpose, combined nature, example, and return value. 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 2 simple parameters, no output schema, and no annotations, the description adequately explains the tool's behavior: finds and taps via natural language, returns success info. Minor gap: doesn't explain failure behavior or limitations (e.g., if element not found).

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 already covers both parameters with descriptions, so baseline is 3. The description provides a useful example mapping parameter to use but doesn't add additional semantics beyond what the schema and example provide.

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?

Clearly states it uses natural language to find and tap a UI element, combining two actions into one. The example makes the purpose concrete and distinct from siblings like 'find_element' or 'tap'.

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?

Provides an example with typical usage ('the Sign In button'), implying when to use it (when element description is known). However, it doesn't explicitly differentiate from alternatives like 'tap' or 'find_element' combined with 'tap', nor suggest when not to use it.

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