click_target

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

With no annotations, the description carries the behavioral disclosure burden. It openly describes the automatic new-tab following and the new_tab: true report, which is a critical and non-obvious behavior. It does not cover failure behavior or broader side effects, but the key quirk is transparently disclosed.

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 front-loaded with the core action and locator methods, then adds one high-value behavioral note with a concrete scenario. Every sentence earns its place, and there is no fluff or repetition.

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?

The description is adequate for normal use: it explains what is clicked, how to target it, and an important tab-following behavior. However, the undefined 'role' and 'reason' parameters, plus the lack of guidance around when to use submit_application instead of a generic click, leave the context incomplete.

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 has 0% description coverage, so the description must compensate. It explains 'name' and 'ref', but completely ignores 'role' and 'reason', leaving two of the four parameters semantically unexplained. This is a meaningful gap for a tool with no schema 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 states a specific verb ('Click') and resource ('a button or link'), and names the two locator modes ('visible/accessible name' or 'ref'). This clearly distinguishes it from sibling tools like fill_field, browser_scroll, or submit_application.

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 gives clear context for when to use the tool: clicking interactive elements by name or reference. It also explains the tab-following behavior with a concrete ATS example, though it does not explicitly state when not to use it or name alternatives like submit_application.

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