browser_click

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

Annotations are absent, so the description carries the full behavioral burden, yet it says nothing about failure modes (element not found), whether clicking waits, or what wait_navigation/tab_index actually change. It only discloses accepted locator formats, which is a small fraction of the behavior an agent needs for a DOM-mutating action.

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 front-loaded sentence with zero padding; the locator list is arguably necessary content. It is efficient, though it trades away completeness for brevity.

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?

An output schema exists so return values needn't be explained, but with no annotations, 0% schema coverage, and a behavior-affecting flag (wait_navigation) left undefined, the description is not sufficient for an agent to call this confidently.

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 0% and two of three parameters (tab_index, wait_navigation) are undocumented anywhere. The description does add real meaning for target by enumerating CSS selector, text, XPath, aria-label, title, and placeholder formats, which partially compensates, but the silence on the other two params leaves a clear gap.

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?

States a specific verb (click) and resource (element) plus the accepted locator strategies, so the agent knows instantly what the tool does. It does not explicitly contrast itself with close siblings like browser_type or browser_focus, which keeps it just below a 5.

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 when-to-use guidance, no prerequisites, and no alternatives named. The agent is left to infer that this is for clicking rather than typing, scrolling, or focusing, with no explicit routing to browser_type/browser_focus for those cases.

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