browser_right_click

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('right click') without revealing expected outcomes like opening a context menu, triggering contextmenu events, or possible failures if the element is not found or not visible.

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, front-loaded sentence that directly states the tool's action. It contains no filler or redundant information, making it exceptionally concise and easy to parse for an agent.

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 simple interaction tool, the description is adequate but incomplete. It fails to mention the primary behavior of right-clicking (e.g., opening a context menu) or any side effects, which would help an agent anticipate the tool's impact. Given no output schema and sparse annotations, the description leaves gaps in expected 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?

The schema already provides a clear description for the single parameter 'selector' as 'CSS selector of the element' (100% coverage). The tool description adds no additional meaning or usage detail beyond what the schema already communicates, so the baseline of 3 is appropriate.

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 'Right click an element' clearly specifies the action (right click) and the target (an element), distinguishing it from sibling tools like browser_click, browser_double_click, and browser_hover. The verb+resource structure is specific and unambiguous.

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 no guidance on when to use this tool versus alternatives like browser_click or browser_hover. It does not mention that right-click is typically used to open context menus or any prerequisites such as element visibility or interactability.

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