browser_click_element

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

No annotations provided, so description carries full burden. It excellently discloses implementation details: trusted events (isTrusted: true), specific event sequence (mousedown + mouseup), protocol method (Chrome DevTools Protocol Input.dispatchMouseEvent), and click coordinates (element center). Crucially, it documents return values ('tag name and trimmed text content') since no output schema exists.

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?

Three information-dense sentences with zero waste. Critical status ([Disabled]) is front-loaded. Sentence 1 defines the action, Sentence 2 details technical implementation, Sentence 3 covers return values and use cases. Every clause earns its place.

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?

Despite no output schema and no annotations, the description is complete. It covers the disabled status, precise behavioral mechanics, return value structure, and appropriate use cases. For a 2-parameter browser automation tool, this provides sufficient context for correct invocation without redundancy.

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?

With 100% schema description coverage, the baseline is 3. The description references 'CSS selector' aligning with the selector parameter and implies the page context, but does not add semantic meaning, format guidance, or examples beyond what the schema already provides for tabId and selector.

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 opens with the critical '[Disabled]' status and clearly states the action: 'Click an element on the page matching the given CSS selector.' It distinguishes effectively from siblings like browser_type_text, browser_hover_element, and browser_press_key by specifying mouse events (mousedown + mouseup) and clicking behavior.

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?

Provides specific positive use cases: 'Useful for submitting forms, toggling buttons, and navigating.' While it doesn't explicitly state negative constraints (e.g., 'do not use for text input'), the verb-specific description and technical details (trusted mouse events) implicitly guide correct selection over alternatives like browser_type_text.

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