mouse_replay

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

No annotations are provided, so the description must disclose behavioral traits. It explains the speed parameter but does not specify how the replay executes (e.g., instantaneous or animated), whether clicks are involved, or any side effects. This is insufficient for a tool with no annotations.

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 short and front-loaded with a star and purpose. Two sentences plus parameter explanations. No wasted words, but could be slightly more structured (e.g., separating behavior from parameters).

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?

While the tool is simple, it lacks mention of return value or behavior when an invalid path is provided. The output schema exists but is not described. For a replay tool, this is adequate but could be more complete.

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 adds significant meaning beyond the input schema: it explains that path_json is a JSON array of {t, x, y} from mouse_record, and clarifies speed values. Schema description coverage is 0%, so this compensation is excellent.

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 replays a recorded mouse path, with a specific verb 'Replay' and resource 'recorded mouse path'. It distinguishes itself from sibling tools like mouse_record (record) and mouse_move (single move).

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?

The description mentions 'from mouse_record', implying it should be used after recording, but lacks explicit guidance on when not to use it or alternatives. It does not contrast with siblings like mouse_move for single movements.

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