joystick_input

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

With no annotations, the description carries the behavioral burden. It discloses a non-obvious side effect: it automatically resumes the emulator if stopped and restores the previous pause state. This is valuable behavioral context, though it does not discuss all possible side effects.

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 and front-loaded, with one sentence for purpose and one for behavioral side effect. Minor spelling errors slightly reduce polish but do not hide the meaning.

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 this simple four-parameter tool with a rich schema and an output schema, the description covers the purpose and the key state-restoration behavior. It could be more explicit about tap duration semantics, but the schema handles most required detail.

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?

All four parameters are described in the schema with enums and purpose, so the schema already provides strong semantic coverage. The description does not add additional parameter meaning beyond what the schema offers.

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 the core action: sending joystick input to C64 joystick port 1 or 2. This is a specific verb and resource, and the joystick target distinguishes it from keyboard_input, though it does not explicitly name sibling alternatives.

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 given about when to choose this tool over keyboard_input or other input methods. It does not state prerequisites or exclusions; the only extra sentence describes automatic resume behavior, not usage context.

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