game_input_state

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

No annotations provided; description only mentions querying but input schema reveals mutation actions. Fails to disclose that the tool can also modify mouse state (warp, mode) or how query results are returned.

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?

Extremely concise (single sentence), but at the cost of omitting critical information about actions and parameters. Adequate length only if the schema provided full context, but it doesn't.

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 no annotations, no output schema, and the tool's dual query/modify nature, the description is insufficient. It does not address return values, side effects, or how to interpret results.

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%, but description adds no extra meaning. It does not explain how parameters like 'action', 'x', 'y', 'mouseMode' relate to the tool's operation, missing an opportunity to clarify usage.

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?

Description specifies verb 'Query' and resources 'pressed keys, mouse position, connected pads', which clearly indicates input state retrieval. However, it omits the modification actions (warp_mouse, set_mouse_mode) implied by the input schema, making it incomplete.

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 siblings like game_key_hold, game_mouse_move, etc. There is no mention of suitable contexts or exclusions.

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