page_press

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

With no annotations, the description carries the full burden of behavioral disclosure, but it only restates the action ('press') already implied by the tool name. It doesn't mention whether the press triggers navigation, key-up/key-down semantics, focus requirements, or any side effects — genuine gaps for an input-mutation 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 front-loaded sentence states the action and example with zero filler. Every word earns its place by either defining the key scope or showing a realistic use case.

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 straightforward 3-param action tool, the description covers the core semantics but omits details like return behavior, errors, or whether key presses require a focused element. Against the rich sibling set, an agent could still succeed by relying on its understanding of key names and page context, but the lack of any behavioral detail keeps it at average.

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 coverage is only 33%, so the description must compensate. It adds value by clarifying the key parameter with a concrete example and the ellipsis implying a known set, but it leaves session_id and page_id entirely unexplained, relying on sibling-tool convention for their meaning.

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 a specific verb ('Press') and resource ('a named key'), immediately distinguishing it from mouse-action siblings like page_click and text-entry tools like page_type or page_fill. The example ('Enter to submit a search box') reinforces the intended action without ambiguity.

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 clear contextual usage via the search-box example, implying this tool is for discrete key presses rather than typing or clicking. It does not explicitly mention alternatives or when not to use it, so it stops short of a 5.

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