browser_click

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It fails to describe what happens on success or failure, whether the tool waits for an element, any side effects (e.g., navigation, state changes), or required permissions. The single sentence offers no transparency beyond the basic 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?

The description is a single, concise sentence that immediately states the verb and resource. It contains no filler or redundant text, and every word 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?

Given the complexity (nested locator object with many properties), lack of output schema, and no annotations, the description is too sparse. It omits critical context: how to uniquely identify a control, definition of 'explicitly shared tab', expected return values, and error scenarios. An agent would need additional knowledge to use this tool correctly.

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?

The description adds no parameter-level information. The schema covers 50% of parameters (locator has a schema description; collaboration_id has only a regex pattern). The description does not explain how to construct the locator, the meaning of 'unique', or the purpose of collaboration_id, leaving the agent to infer from the schema alone.

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 the action ('Click') and the resource ('accessibility-tree control'), with specific qualifiers ('uniquely identified', 'explicitly shared tab') that distinguish it from sibling tools like browser_hover 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 guidance on when to use this tool versus alternatives (e.g., browser_hover, browser_click vs. browser_select) and does not mention prerequisites, error conditions, or when not to use it. The only contextual hint is 'explicitly shared tab', which is insufficient.

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