mouse_up

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

No annotations are provided, so the description carries the full burden. It conveys the drag-termination semantics but says nothing about prerequisites (must a button already be held?), whether unmatched releases error or no-op, or what the call returns.

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?

One short sentence with the core action front-loaded and a parenthetical that earns its place by explaining intent. No filler.

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?

For a one-parameter, enum-constrained input with no output schema, the definition covers the basics. It still leaves the agent guessing about pairing with mouse_down and about the mouse_up vs mouse_release distinction, which matters in this crowded sibling set.

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?

Schema description coverage is 0%, but the single parameter is an enum of left/right/middle, which is largely self-documenting. The description says nothing about the button argument or whether multiple buttons can be held simultaneously, adding little beyond the schema.

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 concrete verb and resource ("Release a mouse button") with a clarifying gloss ("drop the drag"), so the action is unmistakable. It does not, however, distinguish itself from the sibling mouse_release, which an agent must choose between.

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 parenthetical "drop the drag" implies the use case — terminating a drag started by mouse_down — but no explicit timing, prerequisites, or alternative is named. With both mouse_release and mouse_click in the sibling list, the absence of routing guidance is a real gap.

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