game_mouse_drag

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

Annotations are minimal (only title), so the description must cover behavioral traits. It mentions 'drag' implying button hold, but does not explain that the tool simulates mouse input, whether it automatically holds and releases the button, or if it requires the game window to be focused. No side effects or limitations are disclosed.

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 sentence with no wasted words. It is front-loaded with the core action. However, it could be slightly more informative 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?

Given the tool has 6 parameters, no output schema, and no annotations, the description is too minimal. It does not explain return behavior, prerequisites (e.g., game must be running), or details about the drag simulation (e.g., whether the button is pressed and released automatically). This leaves significant 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?

Input schema has 100% coverage (all parameters described). The description adds only the concept of 'N frames' which maps to 'steps'. Since schema coverage is high, the baseline is 3; the description does not significantly enhance parameter understanding beyond the 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 performs a mouse drag between two points over a specified number of frames. The verb 'drag' and resource 'mouse' are specific, and it distinguishes from sibling tools like 'game_mouse_move' (move without drag) and 'game_click' (click without drag).

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 use for dragging but does not explicitly state when to use it versus alternatives like 'game_mouse_move' or 'game_click'. No guidance on prerequisites or when not to use it.

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