click

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

With no annotations provided, the description carries full burden for behavioral disclosure. It states the basic action but doesn't mention what happens after clicking (e.g., UI changes, app navigation), error conditions, permissions needed, or system impacts. The return value description is minimal ('Success or error message').

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 appropriately sized with three clear sections (action, args, returns). The first sentence states the purpose directly. However, the parameter explanations could be slightly more detailed about coordinate systems.

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 (screen interaction), no annotations, and an output schema that only indicates a string return, the description is minimally adequate. It covers the basic action and parameters but lacks behavioral context, error details, and usage guidance relative to siblings.

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?

The description adds significant value beyond the input schema, which has 0% description coverage. It explains that x and y coordinates can be 'absolute or relative 0-1', clarifying the parameter semantics that aren't evident from the schema alone. This compensates fully for the schema's lack of descriptions.

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 ('click') and target ('at the specified coordinates on the screen'), providing a specific verb+resource combination. However, it doesn't explicitly differentiate from sibling tools like 'long_click' or 'gesture', which are similar interaction tools.

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 like 'long_click', 'gesture', or 'press'. There's no mention of context, prerequisites, or exclusions for usage.

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