browser_click

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

Discloses use of 'real CDP mouse events' and caching that survives restarts, adding transparency beyond the schema. However, lacks details on whether the tool scrolls into view, waits for element interactability, or behaviors on errors (e.g., element not found).

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?

Two concise sentences that front-load the main purpose and then explain the caching feature. No wasted words.

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?

Covers main action and caching, but does not describe return value (e.g., success indicator or error) or error handling. Given no output schema and no annotations, more detail on expected outcomes would be beneficial for completeness.

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?

Adds value by explaining the caching mechanism for intent parameter and emphasizing that refs come from browser_snapshot. Schema already has decent parameter descriptions, but the description clarifies the intent caching behavior which is not obvious 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?

Clear verb ('Click') and resource ('element by CSS selector via real CDP mouse events'). Distinguishes from siblings like browser_click_at (coordinate-based) by emphasizing CSS selector and CDP mouse events. Caching mechanism via intent further differentiates.

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?

Description implies caching use case but does not explicitly state when to use this tool versus alternatives like browser_click_at or browser_snapshot for retrieving refs. No guidance on prerequisites (e.g., snapshot needed) or exclusions.

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