browser_mouseMove

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

The description mentions the behavioral trait of simulating human trajectory through segmented movement, but it does not disclose potential side effects (e.g., triggering hover events, coordinate system, or viewport constraints). With no annotations provided, more transparency would be expected.

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 concise, using only two sentences to convey the essential purpose and one additional feature. No redundant wording or unnecessary details are present.

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 action with no output schema, the description covers the core behavior and the optional parameter. However, it does not specify the coordinate system (e.g., viewport vs. page) or whether the tool auto-scrolls to coordinates, which could be a minor gap in full context.

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?

The schema already provides descriptions for all three parameters (100% coverage). The description adds no extra semantic information beyond what the schema states, so it meets the baseline but does not exceed it.

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 (simulate mouse moving), the target (specified coordinates), and the scope (supporting segmented movement for human-like trajectory). It is specific and distinguishes the tool's function without ambiguity.

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 given about when to use this tool versus alternatives like hover or clickAt. The description lacks any explicit or implied usage conditions, leaving the agent without information on when to prefer this tool.

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