right_click

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

No annotations are provided, so the description must carry the behavioral burden, but it only states the action. It does not disclose what happens after the right-click, whether a native context menu appears, how timeouts behave, or what occurs if the element is not found.

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 with no filler. Every word contributes to understanding the tool's core purpose.

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 low-complexity action with full schema coverage, the description is mostly complete: it states the action and target, and the schema documents all parameters. It could add more behavioral context, but nothing critical is missing for basic invocation.

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 100%, so the schema already documents 'by', 'timeout', and 'selector'. The description adds no additional parameter meaning beyond tying the action to 'an element'.

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 names a specific action ('Right-click') and target ('an element'), and the parenthetical '(context menu)' clarifies the intent. It clearly distinguishes right_click from sibling tools like click, double_click, and hover.

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 phrase '(context menu)' implies the tool is used when a context menu is needed, but the description gives no explicit guidance about when to prefer this over click, double_click, or hover. No alternatives are named and no exclusions are provided.

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