scroll

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals only the default half-page behavior, but does not clarify whether the operation is view-only, what the effect on the session is, or any side effects. This is minimal for a tool without annotation support.

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, efficient sentence with no filler. Every word contributes to the meaning, making it highly concise and well-structured.

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?

The tool has an output schema and relatively simple parameters, so the description need not cover return values. However, the lack of usage guidance and minimal behavioral detail leaves some contextual gaps for an AI agent, especially given no annotations.

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 description adds meaning to the 'amount' parameter by noting 'half-pages by default', which helps interpret the default value of 1. However, it does not explain 'session' or 'direction' explicitly, and with 0% schema coverage, it only partially compensates for the missing parameter documentation.

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 uses a specific verb ('navigates') and a specific resource ('scrollback buffer'), clearly distinguishing it from sibling tools like send_keys or capture. The parenthetical 'half-pages by default' adds useful scope.

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 when to use the tool (when you need to navigate the scrollback buffer) but provides no explicit guidance on when not to use it or what alternatives exist. It does not mention relationships to siblings like exit_scroll_mode.

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