browser_mouse_wheel

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

No annotations are provided, so the description carries the full burden. It correctly describes the relative scroll by delta_x and delta_y pixels, implying a one-time simulation. It does not mention side effects or requirements, but the action is straightforward and non-destructive.

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 that immediately conveys the tool's purpose and parameter meaning. There is no wasted text, and the information is front-loaded.

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?

For a simple tool with an output schema, the description adequately covers the core action. However, it does not mention the need for an active browser session or how session_id relates to other browser tools. This omission reduces 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?

The description explains delta_x and delta_y ('by (delta_x, delta_y) pixels'), compensating for the 0% schema coverage. However, the session_id parameter is not mentioned, leaving its purpose unclear. The partial explanation results in a score of 3.

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 action 'scroll the mouse wheel' with specific units (pixels). It distinguishes this tool from siblings like browser_scroll (page scroll) and browser_mouse_move (mouse movement without wheel).

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 explicit guidance on when to use this tool vs alternatives, such as browser_scroll. The usage is implied from the description, but no exclusions or context are provided. A score of 3 reflects the implied usage without further direction.

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