Scroll To

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

With no annotations, the description must convey behavioral traits. It describes scrolling until element is visible and returning a snapshot, but lacks details on side effects (scroll events), prerequisites (element existence), and whether scrolling is incremental. Adequate but not thorough.

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?

Two sentences with zero wasted words. Crucial information is front-loaded: action, target, usage context, and return value. No redundancy or filler.

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 scroll-to-element tool with two well-described parameters and a clear return value (snapshot), the description covers all necessary aspects: what, when, how, and result. No gaps remain.

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%, providing baseline 3. The description adds value by clarifying that eid comes from find results or snapshot, and mentions page_id's default behavior (operates on most recent page). This enhances understanding beyond the schema descriptions.

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 action (scroll to make element visible), the target (element by eid), and distinguishes it from the sibling 'scroll' tool by focusing on a specific element. It also mentions the return of a fresh snapshot, adding purpose completeness.

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?

Explicitly recommends using before clicking or reading an off-screen element reported by find/snapshot, providing clear context. However, it does not state when not to use or directly compare to alternatives like 'scroll', leaving some room for ambiguity.

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