sleeper_keys

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. 'Dispatch key events on active element' hints that focus matters, but it does not say whether keys are held, whether modifier combos are supported, what happens if no element is focused, or what the response looks like. One clause is far too thin for a no-annotation tool.

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?

A single sentence with no padding and the action front-loaded, which is good. But the brevity crosses into under-specification rather than economy — nothing here earns extra credit for tightness when critical detail is absent.

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?

Three-parameter input tool, no annotations, no output schema, and only 33% schema coverage. The description should fill the gaps on key syntax, tab/profile targeting, and focus behavior; it supplies none of that, leaving the definition materially incomplete.

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 33% — only 'profile' is documented in the schema. The description says nothing about 'keys' (array-of-strings format, key names vs. combinations, e.g. 'Control+C') nor about 'tab' (tab targeting). With two of three parameters undocumented anywhere, the description fails to compensate.

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 target: 'Dispatch key events on active element.' That is clearly a keyboard-input operation on the current focus. It does not, however, differentiate itself from the sibling sleeper_press, which appears to be a very similar keyboard tool — an agent cannot tell which to pick from the description alone.

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 gives no condition for when to use this versus sleeper_press, sleeper_type, or sleeper_exec, all of which can emit keystrokes. No prerequisites, no mention of focus state requirements, no exclusions.

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