game_scroll

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

Annotations are minimal (title only), so the description carries full burden. It does not disclose behavioral traits like whether the event is simulated vs real, if it requires game window focus, or how the position relates to the game's coordinate system. For a mouse event simulation tool, this is insufficient.

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?

Single sentence is efficient and clearly conveys the tool's purpose. However, for a tool with four parameters, a bit more detail on usage context could be added without being verbose.

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 input simulation tool with no output schema or annotations, the description is adequate but not comprehensive. It lacks details about coordinate system, event type (e.g., relative vs absolute), and interaction with game state, leaving gaps for an AI agent.

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 description coverage is 100%, so baseline is 3. The description adds no extra meaning beyond what the schema already provides for each parameter (x, y, amount, direction). No additional context or usage hints are given.

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 'Send mouse scroll wheel event at position' clearly states the action (send scroll event) and the resource (mouse scroll wheel) with location. It distinguishes from sibling tools like game_click (click) and game_mouse_move (move) which handle different input types.

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 on when to use this tool versus alternatives such as game_mouse_move or game_click. There is no mention of prerequisites, coordinate system, or whether the game window must be focused.

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