browser_click

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

No annotations provided, so description must disclose behavior. It adds return behavior ('Returns updated page state') and a prerequisite, but does not disclose potential side effects (e.g., navigation, DOM changes, failure modes), which are important for a click 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?

Three concise sentences with no redundant wording. Front-loaded with the action, then useful behavior and prerequisite. Every sentence adds value.

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?

For a simple one-parameter interaction tool, the description covers action, selector method, prerequisite, and return value. It lacks error-handling context (e.g., selector not found) but given the presence of an output schema, it is sufficiently complete for basic invocation.

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 provides only a 'selector' string with no description. Description explicitly states 'by CSS selector', fully clarifying the parameter's purpose. Also 'current page' adds scope, compensating for the 0% schema coverage.

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 clear action 'Click an element' with method 'by CSS selector' and scope 'current page'. Distinguishes from non-browser tools by referencing active browser session. While sibling click_element exists, the browser_* prefix and context make the purpose unambiguous.

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?

Explicitly instructs to call browser_navigate first, establishing a clear prerequisite. Does not mention alternatives or when-not-to-use, so not a 5, but provides sufficient context for the primary use case.

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