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

Annotations already declare destructiveHint=true and idempotentHint=false; the description reinforces this with 'Clicking can submit data or execute destructive application actions,' adding concrete consequence context beyond the flag. It does not describe side effects on app state or failure behavior, so it falls short of a 5 given the annotation baseline.

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, front-loaded with the action and target, then the risk warning. No filler; every clause earns its place.

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?

Output schema exists and annotations cover the safety profile, and the description supplies the workflow prerequisite and consequence warning. Missing sibling differentiation (ui_invoke vs ui_click vs computer_click) is a minor gap for a 9-parameter tool with many overlapping siblings, so a 4 rather than 5.

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% with all 9 parameters documented, so the schema carries parameter semantics. The description only implies that `id` comes from ui_snapshot/ui_find, adding no format or targeting guidance (e.g., id vs label vs name precedence) beyond the schema, so 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?

States a specific verb ('activate'/'click') and resource ('native Accessibility/UI Automation element, such as a button or menu item'), which distinguishes it from ui_snapshot and ui_find. It does not explicitly differentiate from near-siblings like ui_invoke, ui_focus, or computer_click, so the purpose is clear but sibling disambiguation is incomplete.

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?

'after ui_snapshot or ui_find' gives a clear prerequisite workflow and implied when-to-use. There's no explicit when-not-to-use or named alternative (e.g., use ui_invoke for pattern invocation, computer_click for coordinate clicks), which keeps it from a 5.

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