Type literal text

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

Annotations only declare the generic safety profile (readOnlyHint=false, idempotentHint=false, destructiveHint=false). The description adds real behavioral context beyond that: the input goes out as Unicode key events, it is consumed by F8 console and chat/NUI inputs, a focused target input is required first, and it deliberately omits the Enter keystroke. What it does not cover is failure behavior when no input is focused or whether repeated calls append.

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 dense sentences with no filler; the mechanism and its consumer surfaces come first, then the required precondition, then the boundary. Every clause carries information an agent needs.

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?

There is no output schema, so return values are the description's responsibility and they are left unaddressed (success/failure signal, whether text is echoed). For a one-parameter input-injection tool the prerequisite and effect coverage is otherwise strong, so the gap is narrow rather than structural.

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?

The single 'text' parameter is completely undocumented in the schema (0% coverage, bare string type), so the description carries the burden. It does add meaning — the value is typed literally as Unicode key events, not interpreted as a key name or macro — but it stops short of spelling out constraints such as embedded newlines or special-character handling.

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 and mechanism — 'Sends Unicode key events' — and names the exact surfaces that consume them (F8 console, chat/NUI inputs). This cleanly separates it from the sibling key tools (press_key, hold_key, release_key) without the reader needing to open any schema.

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 an explicit precondition ('Open the target input first') and names concrete ways to satisfy it (client_command to focus, or a chat key like T). The closing 'Does not press Enter' is a useful boundary that implies press_key for submission, but the alternative is not stated outright, so it falls just short of fully explicit when/when-not routing.

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