game_touch

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

With no annotations, the description provides only a high-level overview. It does not disclose coordinate system reference, synchronous vs asynchronous behavior, or effects on game state beyond simulation.

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, which is concise, but it overpromises by including 'gestures' without schema support. The structure is front-loaded but lacks completeness.

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 tool with 7 parameters and no output schema, the description misses important context like coordinate system, touch index usage, drag step interpretation, and gesture examples. More detail is needed for correct 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?

Schema coverage is 100%, so the baseline is 3. The description adds no additional semantics to parameters beyond what the schema already provides.

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 it simulates touch press/release/drag and gestures, which distinguishes it from sibling tools like game_click or game_key_press. However, mentioning 'gestures' without corresponding actions in the schema slightly reduces precision.

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_drag or game_key_press. The description lacks prerequisites, exclusions, or context-dependent usage hints.

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