nex_browser_press_key

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

With no annotations, the description carries the full burden and does not disclose whether the keypress dispatches both keydown and keyup, whether it auto-focuses the target, whether it requires an active session/page, or what happens if no element is focused. Only the vague 'or focused element' fallback is conveyed.

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 with no filler, so it is efficient. The brevity crosses into under-specification rather than excess, but on structure alone it is clean.

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 browser keyboard-interaction tool with no annotations and no output schema, the description omits key syntax, modifier handling, focus/target resolution behavior, and connection prerequisites. It is too thin to let an agent call it confidently without inspecting the schema and inferring behavior.

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 75% (pageId, target, sessionId documented), so the baseline is 3. The description adds a little by implying target-vs-focused-element resolution, but it never explains the required 'key' format (e.g. 'Enter', 'Control+A') which is the single mandatory parameter and undocumented in the 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?

States a specific verb (press) and resource (a key) applied to a page or focused element, which is clear enough to understand the action. It does not differentiate from the close siblings nex_browser_key_down / nex_browser_key_up (hold vs. full press) or nex_browser_type, leaving the agent to infer the distinction.

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?

There is no guidance on when to use this instead of key_down/key_up for held keys, type for text entry, or fill_form for structured input. The only contextual hint is the phrase 'selected page or focused element', which implies usage but states no conditions or exclusions.

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