mouse_release_all

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

Annotations already indicate idempotentHint=true and destructiveHint=false. The description adds valuable context beyond annotations: the VM remains locked after release, and vm_unlock must be called separately. This clarifies a subtle behavioral expectation not captured by the schema or 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?

Two concise sentences, zero wasted words, and the primary action is front-loaded. The lock reminder is a necessary addition rather than 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 simple, single-parameter tool with no output schema, the description fully covers the action, scope, and an important post-condition. The agent knows exactly what will happen and what follow-up action is required.

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 100%, and the vm_name parameter is fully documented in the schema. The description does not add parameter-specific detail, but none is needed given the schema's clarity, so the baseline score of 3 is appropriate.

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 uses a specific verb and resource: 'Release every mouse button tracked as held by this session.' It clearly distinguishes this from single-button release tools like mouse_up by emphasizing 'every' and the session-scoped tracking.

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 clearly states when to use the tool: to release all mouse buttons held within the session. It does not explicitly name alternatives like mouse_up for individual releases, but the 'every' qualifier and session-scoped language make the appropriate context evident.

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