terminal.mouse_scroll

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

No annotations, so description carries full burden. It discloses the mechanism (SGR-1006 scroll sequences) and a key condition (mouse mode required). However, lacks details on side effects, error behavior, or return values. Adequate but not comprehensive.

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?

Three sentences, zero waste. First sentence states action, second provides technical detail, third gives use case and prerequisite. Front-loaded and efficient.

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?

Covers mechanism, prerequisite, and typical use. No output schema needed. Could mention failure modes (e.g., mouse mode disabled) but overall sufficient given tool complexity.

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%, so baseline is 3. Description does not add meaning beyond parameter names and types in schema. It restates concepts like 'specific position' which are already clear from schema.

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 states the tool scrolls the mouse wheel at a specific position, using SGR-1006 sequences for interactive TUI programs. It distinguishes from sibling tools like terminal.scroll by specifying mouse wheel and TUI context.

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?

Provides context: useful for scrolling through long content in TUI apps. Includes prerequisite that child process must have mouse mode enabled. Does not explicitly compare to alternatives or state when not to use, but gives sufficient situational guidance.

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