Click Coordinates

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

No annotations are provided, so the description carries the disclosure burden. It adds valuable behavioral context: 'then wait and return an after screenshot' and 'CSS viewport coordinates.' However, it omits potential side effects, permission needs, or details about button variants that could affect behavior.

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, front-loaded sentence that packs essential information: the action, coordinate system, scope, wait behavior, and return value. No word is wasted.

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 covers the core action and result but is incomplete for a tool with 6 parameters. It fails to address button choice, click count, or configuration options beyond wait and screenshot, leaving some aspects uncovered for an agent needing full operational guidance.

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%, so the description must compensate. It explains x/y as coordinates, wait behavior, and the returnScreenshot concept, but it does not describe the 'button' or 'clickCount' parameters, leaving their semantics to the schema's enum/default values without additional context.

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 a specific action: 'Click at CSS viewport coordinates in the selected tab.' It distinguishes the tool from siblings like scroll or press_key by specifying coordinates and the selected tab context, and adds the unique behavior of waiting and returning a screenshot.

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 implies usage for clicking at a location but does not explicitly contrast with alternatives like press_key, type_text, or scroll. It provides clear context (CSS viewport coordinates, selected tab) but no exclusions or when-not-to-use guidance.

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