browser_right_click

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

With no annotations, the description must carry safety and behavior info. It only states the action, without disclosing side effects like opening a context menu, visibility requirements, or whether the action is reversible. This is minimal and doesn't add value beyond the tool name.

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, focused sentence with no redundancy or fluff. It's front-loaded and appropriately sized given the schema's coverage.

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?

Despite the simple action, the lack of usage guidance, behavioral disclosure, and context about context menu effects makes it incomplete. The tool could be used in many scenarios, but the description doesn't explain when right-click is appropriate or what to expect.

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 descriptions for both parameters (ref and element) are detailed and cover 100% of params, so the description doesn't need to add parameter info. The description itself adds no parameter semantics, matching the baseline for high schema coverage.

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' uses a specific verb and resource, clearly distinguishing it from siblings like browser_click and browser_double_click. However, it doesn't explicitly mention the use of aria refs or when to choose this over alternatives, so it's clear but not fully differentiating.

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?

No usage guidance is provided. The description doesn't state when to use right-click vs hover or key press, nor any exclusions or context. The agent receives no direction on selecting this tool over siblings.

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