browser_scroll

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

With no annotations, the description must carry the full behavioral burden, yet it says nothing about waiting for lazy-loaded content, behavior at page top/bottom, whether it is a no-op at boundaries, or what the call returns. Only the granularity of movement (one viewport per page) is disclosed.

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?

A single front-loaded sentence with zero filler; the unit of measurement is the one piece of information an agent needs first.

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 one-optional-parameter tool this is minimally adequate, but with no annotations and no output schema, the description should say which tab is targeted and whether a return value indicates new content or position.

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 the sign convention ('Positive scrolls down, negative up') is already documented. The description adds the unit semantics – a page equals a viewport height – which is genuinely beyond the schema, but nothing about fractional values or defaults.

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?

States a specific verb and resource ('Scroll the target tab') with a clear unit of movement ('whole viewport pages'). It is distinguishable from click/type/snapshot siblings, though 'target tab' is not defined relative to the tab-selection tools.

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?

Usage is only implied by the verb; there is no statement of when to scroll versus calling browser_text/snapshot to fetch content, nor of prerequisites such as which tab must be active. The phrase 'target tab' hints at tab context but does not route the agent.

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