click_element

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

The description discloses a notable behavior (automatic selector healing) and explicitly states the action (click/tap). It does not hide major side effects or expectations, though it does not mention potential errors or side effects like navigation. Given the absence of annotations, this is reasonably transparent.

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 extremely concise, using only two short sentences. It conveys the essential action and a key behavioral feature without any unnecessary words. This is ideal for a simple tool.

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 action, the description covers the core functionality but omits details about return values, error handling, or expected behavior on failure (beyond selector healing). Given the simplicity and the presence of sibling tools, the description is adequate but not fully complete.

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 only parameter, 'selector', has no description in the schema or in the tool description. The description does not explain what format the selector should be (CSS, XPath, etc.) or any constraints. This leaves the parameter meaning largely unspecified.

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's action ('Click/tap') and target ('an element'), which distinguishes it from siblings like fill_element, navigate, and get_content. It is specific and unambiguous.

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 mentions that it automatically heals selectors, which is a useful behavior note, but it does not provide any guidance on when to use this tool versus alternatives (e.g., when to use fill_element instead). No explicit conditions or context are given.

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