browser_scroll_to_coordinates

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

No annotations are provided, so the description must disclose behavior. It only says 'scroll', without explaining scroll behavior (e.g., origin, units, overflow, animation) or providing any safety/reversibility info.

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 extremely short (4 words) but at the expense of informativeness. It is front-loaded but does not earn its place because it lacks necessary detail for proper tool selection.

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's low complexity but lack of annotations and presence of sibling scroll tools, the description is incomplete. It omits usage guidance, behavioral context, and parameter semantics enhancements.

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% with descriptions 'X coordinate' and 'Y coordinate'. The description adds no extra meaning (e.g., units, origin, relative/absolute). Baseline 3 applies.

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 states the verb 'scroll' and resource 'to specific coordinates', but it's ambiguous whether coordinates are absolute or relative, and doesn't distinguish from sibling tools like browser_scroll_by_pixels.

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 vs alternatives like browser_scroll_to_element, browser_scroll_by_pixels, etc. The description is silent on usage context.

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