chrome_click

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds real value beyond them: it explains the trusted/debugger click path and the DOM-click fallback when the debugger cannot attach, which tells the agent about reliability trade-offs.

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?

A single front-loaded sentence with zero filler: mechanism, parameter semantics, and fallback all in one clause chain. Nothing wasted.

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 an action tool with annotations covering the safety profile and no output schema, the description covers mechanism, ref semantics, and failure fallback adequately. Minor gaps: no mention of whether it scrolls into view or what a failed click reports, but these are small for a click primitive.

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 coverage is 60%, and the description clarifies the ref semantics ([#N], element reference) which the schema alone does not. It says nothing about doubleClick, tabId, frameId, or snapshotId beyond what the schema already documents, so it lands at the baseline for partial 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 a specific verb and resource (click an element) and specifies the mechanism (trusted mouse click via Chrome debugger) with a fallback. The [#N] ref format is called out, which is useful given the ref parameter is only typed as integer. Does not explicitly distinguish itself from the sibling browser_click, so it falls short of a 5.

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?

Implies usage (you need a [#N] ref, presumably from chrome_snapshot) and discloses the fallback path, but never states when to prefer this over browser_click or other click siblings. The condition selecting the alternative is left to inference.

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