browser_click

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

With no annotations and only a minimal description, the tool fails to disclose behavioral traits such as side effects (e.g., page navigation, popups), error handling, or requirements for element visibility. The description 'Click an element' assumes the agent understands implications, which is insufficient.

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, concise sentence with no extraneous words. While it could benefit from slight elaboration, it efficiently conveys the core action. However, it may be too terse for a tool with no other documentation.

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 2 required parameters, no annotations, and an output schema not referenced in the description, the description omits essential context. It does not explain what the output contains, error conditions, or any prerequisites (e.g., page must be loaded). The description is incomplete for safe 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?

The parameters 'session_id' and 'selector' have 0% schema description coverage. The description only clarifies that 'selector' is a CSS selector, but does not specify format, allowed values, or how session_id is used. It adds minimal value over the parameter names themselves.

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 verb 'click' and identifies the resource as 'an element (CSS selector) in a session's page'. This distinguishes it from sibling tools like browser_fill (fills form fields) and browser_navigate. However, it lacks specification of what the click triggers (e.g., navigation, event) and could be more precise.

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. For example, it does not mention that browser_click is for clicking interactive elements while browser_fill is for form fields, or that browser_wait might be needed before clicking. The description offers no context for invocation.

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