browser_mouse_wheel

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

The description does not disclose any behavioral traits, such as whether the scrolling is relative or absolute, whether it triggers events, or what effect the parameters have beyond the schema. With no annotations, the description is the sole source of behavioral information, and it fails to provide any.

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 extremely short (one sentence), but this brevity sacrifices informativeness. It is under-specified and does not earn its place as a standalone explanation, relying on an external reference ('see browser_docs').

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 lack of annotations and output schema, the description should provide comprehensive context about behavior, return values, and error conditions. It fails to do so, leaving the agent with minimal actionable 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 coverage is 100% with clear parameter descriptions ('Horizontal scroll amount', 'Vertical scroll amount'). The tool description adds no additional semantic context, so it meets the baseline for well-documented schema.

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 'Scroll the mouse wheel', which is a specific verb plus resource, clearly indicating the tool's purpose. However, it does not distinguish from the sibling 'browser_scroll' tool, leaving ambiguity about the difference between scrolling via mouse wheel and general scrolling.

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 this tool versus alternatives like 'browser_scroll' or 'browser_mouse_move'. There is no mention of context, prerequisites, or when not to use it.

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