user_keyboard_input

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

With no annotations provided, the description carries the behavioral burden. It discloses that the tool simulates press/release events and targets the active playtest simulation, which is meaningful context beyond the schema. However, it does not explain failure behavior, requirements for a running playtest, or whether events are transient within the simulation.

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 focused sentence that immediately states what the tool does. The 'Official Roblox Studio' prefix adds minimal context without bloating the description, and there is no redundant repetition of schema fields.

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 single-parameter tool with no output schema, the description plus schema covers the essential information needed to call it: what input to provide, where it applies, and in what mode. It is nearly complete, though a brief note about requiring an active playtest to be running would fully remove ambiguity.

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%: the schema already documents 'keys' as an array of actions with key names and durationMs. The description adds no parameter-specific detail, so the baseline score of 3 is appropriate since the schema handles parameter semantics.

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 uses a specific verb ('Injects'), a clear resource ('keyboard key press/release events'), and a clear target context ('active Studio playtest simulation'). This clearly distinguishes it from sibling tools like user_mouse_input and character_navigation.

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 establishes the appropriate context by specifying that input is sent to the active Studio playtest simulation, which guides when the tool is applicable. It does not explicitly name alternatives or exclusions, but the domain is clear enough to avoid confusion with mouse input or non-playtest actions.

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