wavexis_mouse_drag_xy

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

Describes side effects (dispatches mouse events, may trigger page interactions) beyond what annotations provide. Also mentions return format. Adds useful behavioral 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?

Concise with front-loaded purpose, usage note, side effects, and return. Efficient use of space, though could be slightly more structured.

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?

Covers purpose, side effects, and return, but lacks detail on parameter semantics and does not differentiate from wavexis_drag. With output schema present, return is less critical, but more context on usage scenarios would improve completeness.

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 description does not explain individual parameters (e.g., steps, button) beyond coordinates. With 0% schema description coverage, more detail is needed to help agents use parameters correctly.

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 tool drags mouse via CDP events from one screen coordinate to another. It uses a specific verb and resource, and distinguishes from sibling tools like wavexis_act.

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?

Explicitly mentions when to use this tool (programmatic coordinate drag) vs. alternatives: wavexis_act for natural-language drag. This provides clear usage guidance.

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