scroll_page

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions lazy loading support but doesn't explain side effects, return behavior, or whether scrolling triggers events. 'Smart' is marketing language without concrete behavioral detail.

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 sentence, which is concise, but it includes a filler emoji and the vague 'Smart'. It's not poorly structured, but the word choice adds little informative value per word.

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?

With 5 parameters, no output schema, and no annotations, a one-line description is severely inadequate. It fails to explain the differences between action types, the purpose of loadAll vs lazy_load, the meaning of x/y coordinates, or any return values or error behavior.

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?

The schema already describes action, loadAll, and selector, and the description adds only a general sense of elements/areas and lazy loading. x and y remain completely undocumented in both schema and description, and the description doesn't clarify coordinate origin or interaction with the action parameter.

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 identifies this as a scroll tool with lazy loading support and the ability to scroll to elements or areas, distinguishing it from sibling tools. However, 'smart' is vague and doesn't enumerate the specific action types, so it's not a perfect 5.

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 provides no guidance on when to use this tool versus alternatives, no exclusions, and no explicit context. The action enum implies usage scenarios, but the description doesn't elaborate on when to choose scroll_page over other browser interaction tools.

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