mouse_drift

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

Discloses use of random Bezier segments and mimics thinking. With no annotations, it partially covers behavior but omits details like whether it's read-only, side effects on mouse position, or if it blocks.

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?

Very concise with three sentences that front-load the core purpose. Every sentence adds value; no fluff.

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 no annotations and an output schema (not shown), the description is adequate for purpose and usage but fails to document parameters, leaving gaps in 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?

Description has 0% schema coverage and does not explain the two parameters (duration_seconds, segments). Names are somewhat self-explanatory, but missing explicit mapping from parameters to behavior.

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?

Clearly describes simulating idle mouse wandering to pass behavioral ML, using Bezier segments. Distinguishes itself from sibling tools like mouse_click_xy or humanize_click by focusing on idle movement rather than deliberate actions.

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 states to call before critical interactions (form submit, button click) to establish human behavior. Provides clear context but does not compare to alternatives or mention when not to use.

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