right_click

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

With no annotations, the description must disclose behavioral traits, but it only states the primary effect (opening context menu). It omits any mention of prerequisites (e.g., accessibility permissions), error handling, side effects, or return behavior, leaving the agent without critical operational context.

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, but it is under-specified rather than concise. It omits essential information about parameters and usage, making it insufficient for an agent to use correctly. The brevity is not a strength here; it is a deficiency.

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 complexity—4 parameters, one nested object, enums, and no output schema—the description is severely incomplete. It fails to explain the target specification, strategy options, modifiers usage, or return_state control, leaving most of the tool's behavior undocumented.

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 description explains none of the parameters. The description does not clarify the 'target' object structure, the meaning of 'strategy', 'modifiers', or 'return_state'. The description adds nothing beyond what the schema already provides, and it fails to compensate for the low 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 clearly states the action: right-click a target to open its context menu. This distinguishes it from sibling tools like left_click and double_click by specifying the exact mouse button and the expected result.

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 this tool versus alternatives (e.g., left_click, double_click, or context-menu alternatives). The description offers no context or conditions for selection.

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