scroll_to

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

With no annotations, the description bears full burden. It only states the basic action, omitting behavioral details like scroll behavior, relative vs absolute scrolling, or behavior when both coordinates and selector are provided. Minimal disclosure beyond the name.

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?

Single sentence is concise but lacks structure. For 4 parameters with optional use cases, more detailed information would be warranted without being verbose. Current phrasing is minimal but not wasteful.

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?

Having 4 optional parameters with no output schema, the description is incomplete. It doesn't explain parameter interactions, default behavior, or scenarios for use. Leaves ambiguities for the agent.

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% so each parameter has a description, giving a baseline of 3. The tool description adds no additional meaning to parameters; it doesn't clarify when to use coordinates versus selector or how to combine them.

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?

Description clearly states the tool scrolls to an element or position using verb+resource. It distinguishes from sibling tools like click_element or navigate, as scrolling is a distinct action. However, it could be more specific about what 'element or position' means.

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 on when to use this tool versus alternatives, no context on prerequisites or when not to use it. The description is a single sentence with no usage instructions.

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