Press a key

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

With no annotations, the description must disclose behavioral traits. It only states the action itself and gives examples. It does not mention whether the key press targets the focused element, whether it triggers navigation (e.g., F5), or any side effects. Minimal behavioral disclosure beyond the obvious.

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 sentence with examples, front-loaded and free of filler. Every word earns its place, making it exemplary in conciseness.

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 one-parameter tool with no output schema, the description is adequate but not complete. It lacks explicit usage guidance and behavioral details, though the simplicity of the tool lowers the burden. Compared to calibration examples, it meets the minimum viable bar.

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 has one parameter (key) with no description, and coverage is 0%. The description compensates by providing example values (Enter, Escape, Tab, F5), giving some meaning. However, it does not explain the expected format or whether combinations like 'Ctrl+A' are supported.

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 a specific verb 'Press' and resource 'keyboard key on the page', with concrete examples (Enter, Escape, Tab, F5). It clearly distinguishes from sibling tools like browser_click (mouse action) and browser_type (text input).

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 implies when to use (for key presses) but does not explicitly contrast with alternatives like browser_type or browser_click. No exclusions or conditions are provided, so usage is only implied.

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