right_click

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

No annotations are available, so the description must disclose behavioral traits like waiting, visibility requirements, or the effect of right-clicking (e.g., opening a context menu). The current description provides none of this, leaving the agent to assume default browser behavior.

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 short sentence, which is concise but lacks structure. It could convey more information (e.g., selector semantics, behavior) without adding significant length.

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 tool's simplicity, the description is too minimal. An output schema exists but is not referenced. The description does not explain the purpose of right-click (e.g., opening a context menu) or any special behavior, leaving the agent with incomplete guidance.

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 0%, meaning the schema does not explain the 'selector' parameter. The description adds no additional meaning; it does not specify the type of selector (CSS, XPath, text) or how it is used. The parameter is essentially undocumented.

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 states the action and the target, using a specific verb and resource. However, it does not differentiate from sibling tools like click or double_click, which could cause confusion when selecting the appropriate tool.

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 guidance is provided on when to use right_click versus alternatives such as click, hover, or double_click. There is no mention of prerequisites, element states, or typical use cases.

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