click

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

With no annotations, the description must disclose behavioral details. It partially does by mentioning waiting for visibility and enablement, but omits information about error handling (e.g., if element not found), side effects, or return value. This is insufficient for a safety-critical action like clicking.

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 sentence, front-loaded and without fluff. However, given the tool's complexity (3 parameters, nested objects), it is too brief to be effective. Conciseness should not come at the cost of completeness.

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?

The description lacks essential information such as how to choose between ref and selector, the meaning of timeoutMs, and any return value or errors. With no output schema and no parameter descriptions, this single sentence is insufficient for an agent to use the tool reliably.

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 0%, meaning the schema itself provides no parameter explanations. The description adds no meaning to the parameters (ref, selector, timeoutMs). Users are left to infer how to specify elements or set timeout, which is inadequate.

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 the precondition ('waiting for it to be visible and enabled'), which defines its purpose. It distinguishes from sibling tools like 'retry_click' by implying a one-time click after ensuring element readiness, but could be more explicit about when to use this vs. alternatives.

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?

No guidance is provided on when to use this tool versus alternatives such as 'retry_click' or 'interact'. The description implies a general click scenario but lacks context-specific usage instructions or caveats.

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