Click

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

Mentions the underlying CDP calls and lack of polling, but does not disclose that clicking may trigger navigation, modal dialogs, or other state changes. The annotation reads readOnlyHint=false, so some behavioral detail beyond the call count would improve 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?

Extremely concise and overloaded with useful clues. The description packs purpose, target identification, and performance characteristics into two short sentences without redundancy.

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 six parameters and no output schema, the description fully covers what an agent needs to invoke this tool correctly. The extra note about CDP calls and no polling adds useful execution context.

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?

All six parameters have meaningful descriptions, including target with format examples, button with enum and default, modifiers list, and doubleClick boolean. Schema coverage is 100%.

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?

Explicitly states it clicks an element and specifies how to identify the target (ref or CSS selector), clearly distinguishing it from coordinate-based clicks or hover actions among sibling tools.

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?

Provides clear action guidance (pass a ref from browser_snapshot or CSS selector) and mentions the number of CDP calls, implying efficiency. Does not explicitly contrast with alternative click methods, but the context of siblings makes the usage clear.

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