game_input_state

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

Despite no annotations, the description fails to disclose that the tool can mutate state (warp_mouse, set_mouse_mode). It presents only a read operation ('Query'), which is inaccurate and hides behavioral traits.

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 overly brief (5 words) and omits critical actions, making it incomplete rather than concise. It fails to earn its place by not covering the tool's full functionality.

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 4 parameters and no output schema, the description should at least mention the three actions (query, warp_mouse, set_mouse_mode) to set user expectations. Its incompleteness leaves the agent underinformed.

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%, and the description adds no additional meaning beyond what is already documented in the schema. Baseline score of 3 is appropriate as no value is added.

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 states 'Query pressed keys, mouse position, connected pads' which identifies the querying purpose, but it omits the 'warp_mouse' and 'set_mouse_mode' actions defined in the schema, making the purpose incomplete and slightly misleading.

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 on when to use this tool versus sibling input tools like game_key_hold, game_mouse_move, or game_input_action. The description lacks any context for selection or exclusions.

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