browser_scroll_to_element

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

With no annotations, the description must disclose behavioral traits, but it only states the action. It does not explain scroll behavior (smooth/instant), element findability requirements, timeout consequences, or what happens if element not found. This lack of detail limits understanding.

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 very concise at 4 words, with no fluff. While it is minimally structured, the front-loaded purpose is clear. A slightly more structured description could improve clarity without adding much length.

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?

The description is incomplete for a tool with multiple siblings and 3 parameters. It lacks information on return value (no output schema), behavior on failure, and integration with the locator parameters. Given the complexity, more detail is needed.

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 100%, so the baseline is 3. The description adds no extra meaning beyond the schema; it does not mention parameters or explain how they are used together. However, it does not contradict 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 to an element' clearly identifies the action (scroll) and target (an element). It distinguishes this tool from sibling scroll tools (e.g., scroll_by_pixels, scroll_to_bottom) which have different scroll behaviors or destinations.

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 like browser_scroll_by_pixels or browser_scroll_to_bottom. Given the presence of multiple scroll-related siblings, explicit usage criteria would help an agent decide correctly.

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