browser_scroll

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'Scroll the viewport' without revealing any side effects, return format, or behavior details (e.g., instant vs. animated, relative vs. absolute). The tool mutates the viewport, but that is inherent. No additional behavioral context is given.

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 and front-loaded with the action, but it borders on under-specification. While there is no fluff, the lack of detail on `amount` and behavior makes it less useful. It is concise but not sufficiently informative to be rated higher on structure.

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, the description is incomplete. It fails to explain the `amount` parameter, does not describe the return value (despite an output schema being present), and gives no prerequisites (e.g., browser must be open). While the tool is simple, the description leaves essential operational details unaddressed.

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 the `direction` parameter ('down' or 'up') but says nothing about `amount`. Since `amount` has a default and no enum, its meaning (pixels, lines, or steps) is left entirely ambiguous. The description adds value only for direction, leaving half the parameters unexplained.

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 a clear verb and resource: 'Scroll the viewport.' It unambiguously identifies the tool's function and distinguishes it from all sibling tools, none of which perform scrolling. The mention of direction further clarifies the scope.

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, nor any context such as 'use after opening a page' or 'for long pages'. Since no sibling tool offers scrolling, the usage is implied but not explicitly articulated. There are no exclusions or alternative routing provided.

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