Click

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the description need not restate that clicking modifies state. However, it adds no additional behavioral context such as possible navigations, event triggers, or prerequisites (e.g., page must be loaded). The description is essentially a restatement of the title, providing no value beyond annotations.

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?

While the description is extremely short (one sentence), it is under-specified rather than concise. It omits critical parameter and behavioral information, and every sentence should earn its place; this one adds almost no value beyond the tool name and title.

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 tool has 6 parameters (1 required) and no output schema, the description is severely incomplete. It provides no information on parameter usage, return values, or side effects. For an interactive browser tool, this level of documentation is insufficient for correct agent invocation.

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?

Schema description coverage is 0%, meaning the JSON schema provides no documentation for any of the 6 parameters. The description fails entirely to explain what 'target', 'button', 'modifiers', 'doubleClick', or 'element' mean or how they affect the click behavior. An agent has no guidance on how to populate parameters correctly.

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 'Perform click on a web page', which clearly identifies the action (click) and the resource (web page). However, it does not differentiate this tool from sibling tools like browser_hover or browser_press_key, which have similar purposes. The name alone conveys the core action, but the description adds no distinguishing context.

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?

No guidance is provided on when to use click versus alternatives like hover, press_key, or drag. With 23 sibling tools including many interaction tools, the absence of usage context makes it hard for an agent to choose correctly.

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