Left Mouse Up

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

Annotations already flag the action as destructive and non-read-only, lowering the burden. The description adds the notion of a 'scoped' hold but does not disclose edge cases (e.g., behavior if no hold is active) or side effects. It does not contradict the 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?

A single, focused sentence with no redundancy. The core action is front-loaded ('Release...'), and the qualifier 'scoped' adds necessary differentiation without padding.

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 the schema covers the only parameter. However, the description omits usage context (when to call, what observing with 'compact' or 'full' means in practice) and no output schema exists, so an agent relies on inferences for surrounding behavior.

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 single parameter return_state is fully documented in the schema with an enum and description, so the description does not need to add detail. It does not mention the parameter, but schema coverage is 100%, meeting the baseline.

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 verb ('Release') on a clearly identified resource ('the scoped left-button hold'). This distinguishes it from sibling tools like left_mouse_down or left_click, though the meaning of 'scoped' is not elaborated.

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 explicit guidance on when to use this tool. The name and 'release' imply it should be used after a hold was established (e.g., via left_mouse_down), but the description does not name the counterpart or discuss alternatives, leaving usage to inference.

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