browser_os_input_click

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

With no annotations, the description carries the full burden. It mentions 'private per-slot X display only', which implies isolation and a display restriction, but it does not disclose side effects, coordinate system, or what happens on failure. The behavioral traits are minimally addressed.

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 concise sentence with no wasted words. It is front-loaded with the action. However, it is under-specified for the tool's complexity, but that is more of a substance issue than a conciseness issue.

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?

Despite an output schema being present, the description does not explain the output or the context of the click. It omits details like coordinate system, display handling, and the meaning of 'slot'. For a tool with four parameters and no annotations, this is incomplete.

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%, and the description does not explain any of the four parameters (x, y, slot, display). It vaguely refers to 'per-slot' but does not define the slot parameter or the display parameter. The agent has to guess their meaning and valid values.

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 clicks via OS input, specifying a private per-slot X display. This distinguishes it from browser-level clicking and other sibling tools like browser_cdp_command or browser_use_tunnel. However, it lacks a verb+resource construction like 'simulate' or 'perform', but 'Click' is clear enough.

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 gives no guidance on when to use this tool versus alternatives. It does not mention prerequisites, use cases, or exclusions. Sibling tools exist for different purposes, but no comparison is provided.

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