game_gamepad

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

With no annotations like readOnlyHint or destructiveHint, the description carries the full burden of behavioral disclosure. It states 'send... input event' which implies a mutation (simulating input), but it does not explain side effects, whether it requires game focus, or if it is a one-shot event.

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 efficient, though it could be slightly expanded with minimal context without losing conciseness.

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?

The tool has 4 parameters and no output schema. The description does not mention return values, error conditions (e.g., invalid index), or the result of the action, leaving the agent without critical context for invocation.

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 the schema already documents all parameters adequately. The description adds no additional meaning beyond the schema, meeting the baseline expectation.

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's function: 'Send gamepad button or axis input event'. It uses a specific verb ('send') and resource ('gamepad input event'), and it implicitly distinguishes itself from sibling tools like game_key_press (keyboard) and game_mouse_drag (mouse).

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 provides no guidance on when to use this tool versus alternatives. It does not mention that keyboard and mouse inputs have separate tools, nor does it specify prerequisites (e.g., connected gamepad) or typical use cases.

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