scroll

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

With no annotations, the description carries the full burden. It does disclose meaningful behavior: scrolling the page and returning either a fresh snapshot or a compact summary when include_snapshot=false. However, it does not explain side effects, failure cases, or what 'compact summary' entails, so coverage is adequate but not rich.

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, front-loaded sentence with no filler. Every clause adds useful information: the action, the direction options, and the effect of the include_snapshot parameter.

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 two-parameter browser action with an output schema present, the description covers the action and both parameter behaviors. It is slightly incomplete only because it does not explicitly route the agent away from sibling tools like snapshot or read, but nothing required to invoke the tool correctly is missing.

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, and it does. It explains the meaningful values of direction ("down" or "up") and clarifies that include_snapshot=false yields a compact summary instead of a snapshot. Both parameters are given semantics beyond their bare schema types.

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 names a specific action and resource: scroll the page, with direction values "down" or "up". The core verb 'scroll' clearly distinguishes this tool from siblings like navigate, click, snapshot, and read, even without naming them.

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?

The description implies the tool is used when the page needs to be scrolled, but it never explicitly states when to use this versus snapshot, read, or navigate. There are no alternative tool names, exclusions, or prerequisite conditions such as requiring a page to be loaded.

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