browser_scroll

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

Since no annotations are provided, the description carries the full burden of explaining behavior, but it reveals nothing beyond the action. It does not mention scroll behavior (e.g., whether it is smooth or instant), how direction and amount interact, or any side effects.

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 brief, which is inherently concise, but it under-specifies the tool's purpose. It is more of a minimal label than an informative explanation, lacking the depth needed for an agent to fully understand the tool.

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?

With two parameters, no annotations, and no output schema, the description is too thin to provide a complete picture. It fails to mention that direction is required, that amount has a default, or how the scrolling is applied, leaving significant gaps in an agent's understanding.

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 input schema has full description coverage for both parameters (direction and amount), so the description does not need to restate them. However, it also does not reinforce or add any contextual meaning to the parameters, resulting in no added value beyond the 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 'Scroll the page' clearly identifies the action and resource, and there is no sibling tool that performs a similar scrolling function. It is direct and unambiguous, though it could be more descriptive about the page context.

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 provides no guidance on when to use this tool versus alternatives. There are no mentions of prerequisites, exclusions, or typical scenarios, leaving the agent to infer usage solely from the tool's existence.

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