safari_press_key

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

With no annotations, the description bears full burden. It only states 'Press a keyboard key' and lists supported keys, but does not disclose behavioral traits such as whether it simulates actual keyboard events, requires focus, or affects page state.

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?

Two sentences with no fluff. The description is compact and front-loaded with the 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?

For a simple key press tool with 100% schema coverage, the description is adequate. It covers supported keys and modifiers. No output schema is needed as the action likely returns nothing.

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 covers both parameters with descriptions. Description adds value by listing examples of 'key' values (enter, tab, arrows) and modifier keys (cmd, shift, alt, ctrl), beyond the schema's generic descriptions.

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?

Description clearly states the tool presses a keyboard key and lists examples (enter, tab, escape, arrows). It distinguishes from sibling tools like safari_type_text and safari_native_keyboard.

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?

Description implies usage for key presses but provides no explicit guidance on when to use this tool versus alternatives like safari_type_text for text input or safari_native_keyboard for native key events.

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