Computer Mouse Down Up

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

With no annotations, the description carries the full behavioral burden. It does disclose that the left button state is held or released and that no cursor movement occurs, but it omits permission requirements, global input-state effects, and whether an unmatched 'up' is safe or a no-op.

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 with the core constraint ('LEFT', 'without moving') front-loaded and no wasted wording. The use-case sentence is compact and directly relevant.

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?

The tool is simple and has an output schema, so return values need not be explained. The description covers the essential input and the key non-movement constraint, but a note about pairing down/up and global input state would make it complete for a mutation-style input tool with no annotations.

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 description coverage is 0%, so the description must compensate. It does so by naming the action values down|up, though the schema provides the default and type; the description does not elaborate on the behavioral difference between the two beyond their names.

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?

States a specific action on a specific resource: hold or release the LEFT mouse button, with the down|up values named. 'Without moving' clearly distinguishes it from computer_drag and computer_click semantics.

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?

Provides a concrete use case: press-drag-press-drag sequences that pyautogui cannot perform in one call. It implies when not to use it through 'without moving', but does not explicitly name computer_drag or computer_click as alternatives.

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