middle_click

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

With no annotations, the description carries the burden and does disclose the key behavioral trait: the frontmost app must be in the session allowlist, otherwise it errors and does nothing. It doesn't cover modifier interactions or side effects beyond that, so not a 5.

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 compact sentences, front-loaded with the action, with the critical precondition second. 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?

A simple click tool with a fully documented schema and no output schema; the description covers the essential precondition (allowlist) that the schema can't express. Missing only minor detail about modifier-holding behavior, which is partly in the schema.

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 coverage is 100%, so the schema already documents both the coordinate and text/modifier parameters in detail (including scaling and modifier syntax). The description adds nothing beyond the coordinate reference already in the schema, giving the expected baseline 3.

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+resource (middle-click at coordinates) and clarifies the gesture (scroll-wheel click), which distinguishes it from sibling click tools like left_click, right_click, and double_click. It doesn't explicitly name those siblings, so it stops short of a 5.

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?

Conveys when the call will succeed via the allowlist prerequisite, but gives no guidance on when to prefer middle_click over left_click or right_click, and no exclusions. Usage is implied by the gesture name rather than explained.

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