wavexis_key_down

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

Annotations are minimal (all false), so the description carries the burden. It states side effect (sends key-down event) and return format (JSON with status). No contradiction with annotations. Could be improved by noting if the event is dispatched synchronously or any error conditions.

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 concise with 4 sentences: purpose, usage context, side effect, return format. No redundant phrases, front-loaded with the key action.

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?

Given the complexity (keyboard events), the description covers purpose, alternatives, side effects, and return. It references CDP and Playwright for context. Lacks mention of prerequisites (session must be open) or error states, but the output schema helps. Nearly complete.

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 description does not detail any parameters; schema description coverage is 0%. However, the input schema itself has property descriptions (e.g., key). The description compensates by saying 'raw keyDown event' and 'mirrors Playwright's API,' but does not add parameter-specific guidance. Baseline 3 is appropriate since the schema already documents parameters well.

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 clearly states it dispatches a raw keyDown event via CDP, using a specific verb and resource. It distinguishes from siblings by recommending wavexis_press_keys for typing and wavexis_act for natural-language interaction.

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 provides explicit guidance on when to use this tool vs alternatives (press_keys, act), but does not mention other related siblings like wavexis_key_up. The context is clear enough for an agent to make a correct choice.

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