dom_click

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

No annotations are provided, so the description carries full burden. It fails to disclose critical behavioral traits such as whether scrolling into view is performed, if it waits for the element to be interactable, or what happens on failure (timeout, not found). Only a post-action observation hint is given.

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?

Two concise sentences, front-loaded with the action. The second sentence is an important contextual instruction. No redundant or extraneous content.

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 a simple click tool with 2 parameters and no output schema, the description covers the basic action and a post-action recommendation. However, it lacks details on error handling, timeout behavior, and element interactivity expectations, leaving noticeable gaps.

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 both parameters (selector, timeout) are already described. The description adds no extra meaning beyond clarifying the tool's action. Baseline 3 is appropriate.

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 'Click on an element' clearly states the verb and resource. It distinguishes the basic click action from sibling tools like 'dom_type' or 'dom_find_element', but does not explicitly differentiate its scope or use cases.

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 a post-action guideline to call 'debug_screenshot' or view source after clicks. However, it does not specify when to use this tool versus alternatives (e.g., 'dom_type' for input interactions, 'js_execute' for programmatic clicks) or 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.