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. It mentions 'bounded distance' but does not disclose whether the scroll is smooth or instant, what happens if the page is shorter than the distance, or how collaboration_id validity is handled. No return value or side effects are described.

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 10-word sentence, which is concise. However, conciseness comes at the cost of missing critical information. It earns its place by stating the purpose but does not provide enough content for a tool with 3 parameters and no annotations.

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?

Given the tool has 3 parameters, no output schema, no annotations, and 31 sibling tools, the description is severely incomplete. It does not address the collaboration_id requirement, contrast with browser_scroll_to, or explain return behavior. The agent would lack sufficient context to use this tool correctly.

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 0%, so the description must compensate. It only hints at distance_px via 'bounded distance' but fails to explain direction (up/down) or collaboration_id. The schema provides enums and constraints but no descriptions, and the tool description adds no meaning beyond 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 clearly states the verb 'scroll' and the resource 'viewport of one explicitly shared tab', with 'bounded distance' hinting at the distance_px parameter. This distinguishes it from sibling tools like browser_scroll_to, which likely scrolls to a specific element. However, the phrase 'explicitly shared tab' is vague and could be clarified.

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 provided on when to use this tool versus alternatives like browser_scroll_to, or on prerequisites such as ensuring the tab is 'explicitly shared'. The description does not mention when not to use it or any context-specific recommendations.

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