chrome_click

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

With no annotations, the description carries full burden but only mentions 'Click an element' and return type. It fails to disclose behaviors such as effects on page state, timing, error handling (e.g., element not found), or whether it uses native events vs JavaScript.

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 concise (two sentences plus Args/Returns), front-loaded with the core purpose, and contains no superfluous information. Every sentence is necessary.

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, the description covers the basic action and parameters. However, it omits usage guidelines, behavioral details, and fails to fully describe error states or return value format, leaving some gaps for an AI agent.

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 description coverage is 0%, but the description explains session_id as 'Session returned by chrome_open_session' and selector as 'CSS selector for target element'. This adds basic meaning beyond the schema (which only has types), but lacks details like selector format or session_id validation.

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 states 'Click an element in an active Chrome CDP session using a CSS selector,' clearly specifying the action (click), target (element), context (active Chrome CDP session), and method (CSS selector). It distinguishes from sibling tools like chrome_type (typing) and chrome_navigate (navigation).

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 does not explicitly state when to use this tool versus alternatives like chrome_type or chrome_wait_for. It implies a requirement for an active session from chrome_open_session but offers no guidance on exclusions or comparative use cases.

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