page_press

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

The description adds useful behavioral context beyond the annotations, especially the key fact that input is delivered via background CDP and does not activate the tab. The annotations already indicate destructive potential and non-read-only status, and the description does not contradict them.

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, tightly packed sentence that front-loads the action and includes only essential qualifiers. No filler or redundant restatement of the tool name.

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?

The description covers the core invocation details for a simple tool, and the presence of an output schema plus annotations fills in return and safety information. Minor ambiguity remains around the exact key-chord syntax and the optional session_id behavior, but the description is largely complete for correct use.

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?

With 0% schema description coverage, the description adds meaning to keys_csv by explaining that it accepts a key or comma-delimited modifier chord. It is less explicit about timeout and session_id, but those parameter names are reasonably self-explanatory and the description's clarification is valuable beyond the bare schema.

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 action ('Press a key or comma-delimited modifier chord'), the target ('in a specific tab'), the mechanism ('background CDP input'), and a distinguishing behavior ('without activating the tab'). This makes it easy to tell apart from siblings like page_click and page_type.

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 clearly communicates when to use this tool: for keyboard input in a background tab without activating it. It does not explicitly mention alternatives or say when not to use it, but the context is clear enough for an agent to select it over page_type or page_click.

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