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 only states the action and targeting methods, omitting any side effects, error handling, prerequisites, or state changes. The lack of transparency is significant given the tool's complexity.

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 (single sentence, 10 words) and front-loaded with the action and targeting methods. No redundant or extraneous information is present.

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 has 30 parameters and no output schema, the description is vastly incomplete. It fails to contextualize the many optional parameters (e.g., session, platform, device selection, snapshot options) or explain how they relate to the core action, leaving the agent without sufficient guidance.

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 coverage is 100%, so the baseline is 3. The description does not add meaning beyond what the schema already provides for parameters. It only mentions targeting methods, which are thoroughly documented in the 'target' parameter schema.

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 or tap') and the resource ('semantic UI target') with specific targeting methods (ref, selector, or point). This is specific and distinguishes from sibling tools like 'press' (keyboard) and 'longpress' (hold).

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 among the 49 siblings. No when-not-to-use or alternative suggestions are given, leaving the agent to infer based only on the tool name.

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