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

Annotations already declare destructiveHint=true, readOnlyHint=false and openWorldHint=true, so the safety profile is covered. The description adds a useful caution ('inspect the target and resulting menu before selecting any command'), which implies the risk lies in the follow-up menu choice rather than the click itself. It does not explain device prerequisites, backend behavior, or what the interaction does to existing UI state, so it only modestly exceeds the annotation baseline.

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?

Two short sentences, front-loaded with the purpose and followed by a relevant safety caution. No filler, though the second sentence is advisory rather than definitional.

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?

An output schema and rich annotations exist, so the description need not explain returns or safety flags. Still, an agent calling this tool must know how the 'button' enum interacts with a right-click-specific tool and when 'backend' matters, neither of which is addressed. Adequate but with a meaningful gap for a 5-parameter destructive interaction tool.

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 all five parameters are documented, and the baseline is 3. The phrase 'verified coordinate' adds a small hint that x/y should come from a prior inspection, but the description does not address the device requirement, backend choice, or the ambiguous interaction between this tool and the redundant 'button' parameter.

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 states a specific verb and resource: 'open a native context menu by right-clicking'. An agent can tell this is a right-click gesture rather than a general click. However, it does not distinguish itself from the sibling pointer_click, which exposes a 'button' enum including 'right' and could plausibly do the same thing.

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?

'Use this to open a native context menu' gives a clear triggering condition, and the instruction to inspect the target and resulting menu supplies workflow context. It stops short of naming alternatives (e.g., pointer_click with button=right) or stating when not to use it, so it is not a 5.

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