browser_click

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

With no annotations, the description should disclose all behavioral traits. It partially covers execution timing and timeout handling, but fails to describe what happens during a click (e.g., page load, navigation, error cases). The core action behavior is not transparent.

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 short (two sentences) but poorly structured. The first sentence is awkward and does not front-load the core purpose. It could be more concise and better organized, but it is not overly long.

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 8 parameters, an output schema, and no sibling differentiation, the description is incomplete. It omits explanation of return values, parameter formats, and the tool's overall behavior beyond timing.

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%, so the description must add meaning. It mentions several parameters (expected_runtime_seconds, timeout_seconds, etc.) but does not explain their function in detail. The required parameters selector and session_id are completely undocumented.

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 does not explicitly state that the tool clicks an element in a browser. It only mentions 'browser_click' and then discusses execution timing, leaving the core action implied. A clear verb+resource phrase like 'Click a specified element in the browser' is missing, making it vague.

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 browser_click versus sibling browser tools (e.g., browser_navigate, browser_type). The description does explain when to choose different on_timeout behaviors, but that is secondary to the tool's primary usage context.

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