scroll_to_element

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

With no annotations provided, the description carries full burden for behavioral disclosure. It only states the primary action (scroll to bring element into view) but omits important behaviors: how it handles element not found, timeout, scrolling mechanism (smooth/instant), and whether it scrolls a parent container or the whole page. The timeout parameter is not referenced in the description.

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 sentence that directly states the purpose. It is front-loaded and contains no unnecessary words. However, it may be overly concise, missing context that could be added without verbosity.

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 a fully documented schema and no output schema, the description is minimally adequate. It gives the core action but lacks context on behavior details like waiting, error handling, and locator strategy. More completeness would improve usability.

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 baseline is 3 per guidelines. The description adds no additional meaning beyond the schema; it does not mention the parameters 'selector', 'by', or 'timeout'. However, since the schema fully describes them, the description is not required to repeat, so score is adequate.

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 tool scrolls the page to bring an element into view. It uses a specific verb ('scroll') and resource ('element'), which differentiates it from siblings like 'scroll_by' that scroll by pixels. However, it does not explicitly distinguish from all siblings, and lacks a title.

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 given on when to use this tool over alternatives such as 'scroll_by', 'scroll_to_bottom', or 'scroll_to_top'. The description does not mention prerequisites, when-not-to-use, or conditions for selecting this tool.

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