click

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

With no annotations provided, the description carries the full burden of disclosing behavior. It explicitly reveals a key safety guard: 'Blocked when the element looks irreversible unless confirm is true.' This goes beyond a generic 'click' description and warns about potential destructive actions, though it does not detail other side effects like navigation.

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 exceptionally concise: two sentences, front-loaded with the action verb, and every word adds value. There is no redundancy or fluff.

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 simple click tool with a fully documented input schema, the description plus schema is sufficient to invoke the tool correctly. It covers purpose, input mechanism, and the important irreversible-action guard. Minor details like error behavior when the element is not found are absent but not critical for basic use.

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?

The input schema already provides 100% parameter coverage, describing 'ref' as an element ref or selector and 'confirm' as a flag for human approval. The description merely restates part of this ('ref from snapshot') and adds no new semantic detail beyond the schema.

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 uses a specific verb ('Click') and resource ('an element by its ref from snapshot'), making the tool's action unmistakable. It also differentiates from sibling tools like 'press' and 'mouse' by clarifying the mechanism (snapshot ref).

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 phrase 'by its ref from snapshot' clearly indicates the intended input source and when this tool should be used. It does not explicitly mention when not to use it or alternatives, but the context is clear enough for a competent agent.

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