Click Element

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

Annotations provide destructiveHint=true, which is consistent with clicking. The description adds that observe returns a compact before/after summary, a behavioral trait not in annotations. No contradiction. It does not mention timeout behavior or what happens if element not found, but the schema handles that.

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 succinct sentences, no fluff. The most important information (what it does, selector types) is front-loaded.

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 a click tool with a clear action, the description adequately covers purpose, selector syntax, and an optional feature (observe). It is complete given the schema and output schema richness.

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?

With 100% schema coverage, baseline is 3. The description adds meaning by clarifying selector syntax and explaining the observe parameter's effect, going beyond the schema's brief descriptions.

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 tool clicks an element, specifying both CSS selector and XPath support. This clearly distinguishes it from sibling tools like element_find (which only finds) or element_type (which types).

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 explicit guidance on selector syntax: bare selectors are CSS, and text:... for text matching. It also mentions the observe parameter for page change summary. However, it does not explicitly state when to use this tool versus alternatives like page_click_xy (coordinate-based click).

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