browser_keyboard_shortcut

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

No annotations are provided, so the description must carry the full burden of behavioral disclosure. It states the action but lacks detail on focus requirements, timing, side effects, or whether the shortcut is sent to the active page or element. This is insufficient for a tool that simulates complex keyboard interactions.

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 concise with two sentences. The first sentence states the action, and the second provides useful examples. It could benefit from a slightly more structured explanation of parameters, but overall it is efficient.

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?

Given the lack of annotations and output schema, the description does not adequately cover behavioral expectations. It explains the basic function and provides examples, but omits parameter details and contextual prerequisites, making it incomplete for reliable agent 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 and 5 parameters (including 4 boolean modifiers), the description provides no explicit explanation of each parameter. It only illustrates combinations via examples, leaving agents to infer parameter meanings without documentation.

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 tool's purpose: 'Send a keyboard shortcut with modifier keys.' The examples (Ctrl+C, Ctrl+V, etc.) effectively illustrate the functionality and distinguish it from sibling tools like browser_press_key (single key) and browser_type (text input).

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 implicitly guides usage through examples but does not explicitly state when to use this tool versus alternatives like browser_press_key or browser_type. No exclusion criteria or prerequisites are provided.

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