browser_click

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

With no annotations, the description takes on full disclosure responsibility. It mentions the key behavior 'Waits for the element to be clickable before clicking,' but does not disclose other behavioral traits like scrolling to element, error handling, or return value, limiting transparency.

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 extremely concise at two sentences. The first sentence front-loads the main purpose, and the second adds a critical behavioral detail without redundant or superfluous content.

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's simplicity and the presence of an output schema, the description sufficiently covers the core action and waiting behavior. However, it could briefly mention prerequisites (e.g., element must exist in DOM) or post-conditions, though not strictly necessary.

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?

Since input schema coverage is 100%, the description does not need to add meaning for each parameter. It does not elaborate on selector types or timeout semantics beyond the schema, so it meets the baseline without adding extra value.

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 'Click an element on the page' with a specific verb and resource, leaving no ambiguity about the tool's primary action. It effectively distinguishes itself from sibling browser interaction tools like browser_type or browser_select.

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?

The description provides no explicit guidance on when to use this tool over alternatives or when not to use it. The usage context (clicking when element is clickable) is implicit but lacks comparison with other tools or exclusion criteria.

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