Tuanjie Input Simulator

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

Annotations already convey destructive/non-read-only/non-idempotent behavior. The description adds that virtual devices can be created/destroyed and that extra parameters pass through unchanged, but it does not disclose effects such as OS-level input injection, required Play Mode state, or cleanup obligations.

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?

Two sentences with no filler; the purpose is front-loaded and the action list is compact enough to scan. Every sentence earns its place.

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 multi-action input tool with no output schema and no parameter descriptions, this is under-specified. An agent cannot determine required parameters for each action, ordering dependencies (e.g., creating virtual devices first), or return/error behavior, which are necessary to invoke the tool correctly.

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 0%; the only documented parameter is the action enum. The description repeats the enum and adds a pass-through note, but it never explains action-specific parameters (e.g., coordinates, buttons, key codes, text content), leaving the main invocation detail undocumented.

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?

States a specific verb 'simulates' with clear resources: mouse, keyboard, and virtual input devices. The supported action enum is listed, and 'input simulator' clearly separates this from the sibling Unity editor/tooling tools.

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?

Gives a clear context: 'primarily in Play Mode' and enumerates exactly which actions are supported. It does not explicitly exclude alternatives, but with a single input-focused tool among siblings the usage context is reasonably clear.

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