Desktop: Multi select

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

Annotations already declare readOnlyHint=false and destructiveHint=true. The description adds useful prerequisite context (the desktop_permission requirement) and the Ctrl-hold mechanic, but it never explains why this is destructive or what state it alters (e.g. existing selection being replaced), and the Ctrl behavior partly duplicates the schema's hold_ctrl description.

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 sentences, zero waste, and the core action plus Ctrl mechanic is front-loaded with the permission prerequisite following. Nothing needs to be trimmed or moved.

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 GUI click tool with no output schema and full schema coverage, the description covers the action, the selection targets, the modifier-key mechanic, and the permission gate. The main omission is any statement of what the destructive side effects actually are.

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% and both parameters are documented in the schema, including the hold_ctrl multi-select semantics and the [x, y] pair format. The description adds no format or ordering detail beyond that, so the baseline 3 applies.

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 states a specific verb and resource: clicking multiple screen coordinates with Ctrl held to multi-select. The word 'multiple' implicitly distinguishes it from desktop_click's single click, but no sibling is named explicitly, so it falls 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?

It gives concrete usage context ('files, checkboxes, list entries') and a prerequisite ('requires desktop_permission in the active mission step'). It stops short of stating when to prefer this over desktop_click or desktop_ahk, so no explicit alternative routing.

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