session_scroll

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

Annotations only provide a title, so the description carries the behavioral disclosure burden. It discloses direction and magnitude but does not mention side effects, whether it affects the current session page, or whether it preserves navigation history. Adequate for a benign viewport action, 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?

A single sentence with no wasted words, front-loaded with the action and key unit of measurement. Every element earns its place.

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 action with full parameter schema coverage and no output schema, the definition provides enough information for selection and invocation. It could explicitly state that scrolling applies to the current page of the given session, but the session_id parameter and sibling context make that inferable.

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 input schema already documents all three parameters with descriptions and defaults, so schema coverage is 100%. The description repeats 'up/down' and 'viewport-heights' but adds no new semantic detail beyond what the schema provides.

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 the exact operation (scroll), the resource (the page), and the unit of measurement (viewport-heights), making it clear what the tool does. It is also clearly distinct from sibling tools like session_navigate and session_click.

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 explicit when-to-use guidance or alternatives are named, but the action is self-descriptive and no sibling tool provides scrolling. The usage context is implied rather than explicitly stated.

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