click

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

The description does not disclose any behavioral traits beyond the basic click action. For example, it does not mention whether it scrolls to the element, waits for visibility, or triggers navigation. With no annotations, this omission leaves the agent unaware of potential side effects or requirements.

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 a single short sentence, which is concise but lacks structure. It could include additional context without becoming verbose, such as noting that the click is immediate or that it triggers standard DOM events.

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?

Given the complexity of the browser automation domain and the number of sibling tools, the description is incomplete. It does not address when to use 'click' over 'click_at' or how it interacts with page state. An output schema is absent, but even without one, more context is needed.

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 one parameter 'selector' with no description. The description adds that the selector is CSS, which provides some semantic meaning. However, given 0% schema coverage, more detail (e.g., expected format, supported CSS selectors) would significantly improve agent usage.

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 that the tool clicks an element using a CSS selector. The verb 'click' and the resource 'element' are specific. However, it does not differentiate from sibling tools like 'click_at' or 'hover', which also involve clicking but with different input methods.

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 no guidance on when to use this tool vs alternatives. With sibling tools like 'click_at', 'hover', and 'fill_form', an agent would benefit from knowing scenarios where this tool is preferred, but none is provided.

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