mouse_release_all

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

Annotations only state idempotency and non-destructiveness. The description adds valuable context: the release is scoped to 'this session', and the VM lock is preserved, requiring a separate vm_unlock call. This goes beyond the structured hints and warns the agent about session lock behavior.

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 consists of two concise sentences: the first states the primary action, the second clarifies an important side effect. No fluff or repetition of schema annotations. Every word adds value and the structure is front-loaded with the core purpose.

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 tool with no parameters and no output schema, the description fully covers what the tool does, its session scope, and the follow-up action needed (vm_unlock). It is complete enough for an agent to select and invoke it correctly without further information.

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 tool has zero parameters, so the description is not required to explain parameter details. Baseline for no-parameter tools is 4, and the description correctly focuses on the action and its side effects rather than inventing unnecessary parameter explanations.

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 ('Release') with a clear resource ('every mouse button tracked as held by this session'). It distinguishes itself from siblings like mouse_up (which releases a specific button) and keyboard_release_all (which handles keyboard). The scope 'tracked as held by this session' adds precision.

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 implies when to use this tool: when you need to reset all mouse held states for the session. It does not explicitly name alternatives (e.g., mouse_up for individual buttons), but the context of session tracking and the note about the VM remaining locked provide clear situational guidance. It lacks an explicit 'use instead of...' but is still helpful.

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