browser_click

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

With no annotations, the description must fully disclose behavior. It only states 'click' without specifying whether it scrolls to the element, waits for visibility, or raises errors if the element is not found. Behavioral traits like event triggering or navigation consequences are omitted.

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?

A single sentence that is front-loaded with the core action. No redundant words; every part contributes to understanding.

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 action, the description is minimally adequate but lacks details on error handling, scrolling behavior, waiting, or return values. Given no output schema and no annotations, more context would be beneficial for reliable agent usage.

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 adds context by grouping targeting methods (CSS selector and text content) and introducing ARIA label, though that is not reflected in the schema. This provides some additional meaning beyond the schema 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 identifies the action ('click') and the resource ('element in the browser'). It lists three targeting methods (CSS selector, text content, ARIA label), but the ARIA label method is not reflected in the input schema, which may cause slight confusion. Nonetheless, it effectively distinguishes from sibling tools like browser_type or browser_scroll.

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, prerequisites, or conditions like element visibility. For example, it does not mention that the element must be present or that the tool does not implicitly scroll or wait.

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