send_joypad_motion

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

The description adds behavioral context by stating it 'simulates analog input with float precision,' implying the event is synthetic. It also mentions the run_interactive dependency. While it doesn't detail side effects on the running game, this goes beyond the minimal annotations (readOnlyHint false, destructiveHint false).

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 concise—two sentences that front-load the main purpose and include the key alternative and prerequisite. Every sentence earns its place with no filler.

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 low-complexity tool with complete schema coverage and minimal annotations, the description provides the essential context: what it does, when to use it (or not), and a critical prerequisite. It could mention return behavior, but the lack of an output schema makes that less critical.

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% with detailed descriptions for all parameters. The description adds only the 'float precision' nuance, which is marginal since the schema already specifies value ranges. It doesn't significantly enhance 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's function: sending a gamepad analog stick or trigger axis event with float precision. It distinguishes itself from sibling tools like send_joypad_button (button events) and send_input (input actions), making its purpose unambiguous.

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 explicitly states 'For input actions, prefer send_input,' providing a clear alternative for a different use case. It also notes the prerequisite 'Requires run_interactive,' giving concrete guidance on when this tool is applicable.

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