page_press

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly states that input is sent via background CDP and that the tab is not activated, which are meaningful behavioral facts beyond the schema. It could add more about timing, failures, or whether modifiers are released, but the core behavior is clear.

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 entire description is one tightly worded sentence that front-loads the action and embeds the key constraints. There is no filler, and every phrase earns its place.

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 tool's core behavior and there is an output schema, so return values need not be explained. However, without annotations, it lacks explicit guidance on when to choose this over sibling tools like hotkey or page_click, and it leaves two parameters semantically under-specified. It is minimally adequate but not complete.

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 description coverage is 0%, so the description must compensate for all three parameters. It clarifies keys_csv by mentioning 'comma-delimited modifier chord', but timeout and session_id are not explained at all. The parameter names are self-descriptive, but the description adds only partial value for one of three parameters.

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 ('a specific tab'), and clearly distinguishes this tool from siblings by specifying 'background CDP input' and 'without activating the tab'. This makes its purpose unambiguous and differentiates it from hotkey or page_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?

The description implies when to use this tool: when a key or modifier chord must be sent to a specific tab without bringing it to the foreground. It does not explicitly name alternative tools or list exclusions, but the 'without activating the tab' qualifier provides clear contextual selection guidance.

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