Click Coordinates

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

Beyond the annotations (readOnly=false, destructive=true), the description and schema detail the movement profile: direct single move vs deterministic 24-step bounded cubic Bezier with 8-14ms intervals, optional explicit delay, and press/release behavior. This meaningfully discloses how the click is executed.

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?

One front-loaded sentence includes the main action, coordinate basis, trajectory options, and delay without filler. Every clause earns its place.

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 rich input schema, annotations, and presence of an output schema, the description covers purpose, trajectory, and click semantics sufficiently. The main gap—alternatives—is captured under usage guidelines, not completeness.

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?

Input schema coverage is 100% with clear descriptions for all six parameters (x/y coordinates, button, element, profile, delay), so the description adds little beyond summarizing the trajectory and delay. Baseline 3 is appropriate.

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?

Description names a specific action (move pointer to exact CSS pixel coordinates) and a resulting button press/release, clearly distinguishing this coordinate-based click from element-based siblings like element_click or movement-only page_pointer_move.

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 phrase 'exact CSS pixel coordinates' gives clear context for when this tool is appropriate, and the delay parameter description adds an important exclusion (not for moving targets). It does not explicitly name alternatives like element_click, so it falls short of full sibling differentiation.

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