Send keys to DOS target

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

The annotations already declare readOnlyHint=false, so the mutating nature is known, but the description adds minimal context beyond 'input queue.' It fails to disclose that the tool collects terminal output after injecting keys, which is implied by the settle_ms parameter in the schema but not mentioned in the description. This is a significant behavioral gap.

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, front-loaded sentence with no filler. Every word is relevant.

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?

While the schema is fairly rich, the description is too terse to provide context such as when to use the tool, what happens after injection, or how to set up the target. The existence of an output schema covers return values, but the description itself leaves gaps in operational context for a tool with five optional parameters.

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 schema covers 80% of parameters with descriptions, so the baseline is 3. The description does not add any parameter-specific meaning; it only gestures at 'text and named keys,' which the schema already explains. It does not clarify the ambiguous 'target' parameter.

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 the specific verb 'inject' and identifies the resource as 'the target's input queue,' clearly distinguishing it from sibling tools like capture_screen, upload_file, and get_capabilities. It adds the detail of 'text and named keys' which maps to the parameters. This is a clear, non-tautological statement of function.

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 contains no guidance on when to use this tool versus alternatives, nor any prerequisites or exclusions. It does not mention that the target must be active or how to choose among multiple targets, leaving the agent to infer usage from the name and schema alone.

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