nanokvm_scroll

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

With no annotations provided, the description must disclose behavioral traits itself. It does add the meaningful detail that positive amounts scroll down and negative amounts scroll up, which is beyond the schema. However, it does not mention any limitations, side effects, or whether the scroll is relative to the current position.

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 extremely concise yet effective. It leads with the core action and then immediately explains the only parameter. Every word adds value, with no redundancy or filler.

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 that the tool has only one parameter and an output schema exists, the description covers the essential parameter semantics. However, it lacks context about when to use this tool in favor of other input methods, and does not mention any prerequisites or device connectivity requirements. This leaves some gaps for an agent to fully determine appropriate usage.

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 only specifies 'amount' as an integer. The description enriches this by explicitly defining the semantic meaning: 'Positive = scroll down, negative = scroll up.' This is essential information not present in the schema, making the parameter fully understandable.

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 'Scroll the mouse wheel' clearly states the tool's function with a specific verb and resource. It distinctly separates this tool from siblings like nanokvm_send_key, nanokvm_tap, and nanokvm_move, which handle other input actions.

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 guidance is provided regarding when to use this tool versus alternative input tools such as nanokvm_click or nanokvm_tap. The description only states what the tool does, not the context or exclusions.

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