kitty_scroll

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

No annotations are provided, so the description carries full burden. It describes scroll actions, which are typically non-destructive, but does not explicitly state safety, reversibility, or system impact. The description is adequate but could be more transparent about behavioral traits.

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 concise, front-loading the purpose, and includes a compact list of examples. Every sentence serves a purpose with no unnecessary text.

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?

Given the tool's simplicity, no output schema, and 100% parameter schema coverage, the description covers key usage patterns. It could briefly mention the match parameter's role or scrolling constraints, but overall it is sufficiently complete for an agent to invoke the tool correctly.

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%, with descriptions for both parameters. The description adds value by giving concrete examples and syntax for the amount parameter, clarifying units and directions. It does not elaborate on the match parameter beyond the schema, but overall it enriches understanding of the amount 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 states the tool scrolls kitty window content and lists supported scrolling modes (lines, pages, start/end, prompts, unscroll). It uses a specific verb 'scroll' and resource 'kitty window', effectively distinguishing from sibling tools like kitty_send_key or kitty_get_text.

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 detailed usage examples for the amount parameter, guiding the agent on valid inputs. However, it does not explicitly mention when not to use this tool or suggest alternatives, but the context of sibling tools implies it is the correct tool for scrolling actions.

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