Keyboard Press

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

The description adds little beyond annotations. It states 'active page element' but does not discuss potential destructive behavior (e.g., submitting forms) or limitations (e.g., only works on focusable elements). Annotations already indicate destructiveHint=true, but no further context is provided.

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, well-structured sentence that immediately conveys the tool's purpose. No extraneous words or repetition.

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 simple tool with two parameters and good annotations, the description is minimally adequate. However, it lacks usage context and does not explain how this tool differs from similar ones like element_type, which is a notable gap.

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?

Input schema coverage is 100%, with both parameters documented. The description adds the context of 'active page element' but does not enhance understanding of the parameters beyond the schema. Thus, score is at baseline.

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 the tool sends keyboard text/keys to the active page element, which is a specific action on a specific resource. It distinguishes this tool from siblings like element_type (which types into a found element) and element_click.

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?

No guidance on when to use this tool versus alternatives. For example, it doesn't mention that element_type is for typing into a specific element, while keyboard_press sends keys to whatever element is currently active. This omission could lead to incorrect tool selection.

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