chrome_click

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

No annotations are provided, so the description carries full burden. It discloses only the basic action (clicking) but does not mention behavior such as whether it waits for the element to be interactable, what happens if no match is found, or if scrolling is involved. This is insufficient for a safe operation.

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 sentence with no fluff, but it is too brief given the missing parameter information. Front-loading the purpose is good, but the conciseness sacrifices necessary detail.

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 no output schema, no annotations, and an empty input schema, the description is far from complete. It lacks information on return value, error handling, and the critical parameter that should exist. An agent cannot correctly invoke this tool based solely on the provided description and schema.

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 shows zero parameters, yet the description implies a CSS selector parameter is required. This contradiction is highly misleading. The description does not add meaning; it conflicts with the schema, making the tool unusable as specified.

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 ('clicks'), the target ('first element matching a CSS selector'), and the context ('current Google Chrome tab'). It distinguishes from sibling tools by specifying the type of interaction (click vs. fill, type, navigate).

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 versus alternatives (e.g., chrome_type, chrome_fill_form) or any prerequisites (e.g., page must be loaded, element must be visible). No exclusions or recommended scenarios are given.

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