Emergency stop

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

Annotations only declare it is a non-read-only, idempotent, non-destructive write; the description adds real detail about scope of effect — pending queued actions are discarded, any held button is released, and a stop signal is pushed to the browser companion. It does not say what happens if nothing is pending (silent no-op vs error), which is the remaining gap.

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 sentence, front-loaded with 'Immediately', and every clause names a distinct effect of the stop. Nothing is repeated from structured fields.

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?

With an output schema present the description needn't explain return values, and the annotations carry the safety profile. For a zero-param emergency tool this is nearly complete; only the behavior when no action is in flight is unstated.

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?

Zero parameters, so there is no parameter semantics to document; baseline 4 applies. Nothing in the description misleads about inputs.

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?

Uses precise verbs (cancel, drain, release, send stop) against concrete resources (current mouse action, queued actions, held buttons, browser companion). No sibling tool overlaps this 'halt everything' semantics, so an agent can identify it without opening a schema.

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 adverb 'Immediately' and the emergency-stop title imply the usage context (abort a live action or clear a stuck queue), but the description never states when to prefer it over siblings such as mouse_status or computer_observe, nor any precondition for calling it.

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