aua_press_button

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

Annotations already flag this as a non-read-only, non-idempotent, open-world mutation, and the description usefully adds that it presses exactly once, that Enter may submit, and that an authorization is required. It stays silent on what the 'observe' capture returns and on failure/retry behavior for a non-idempotent action.

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 short clauses, front-loaded with the action and scope, with no filler. The wording 'volume' rather than up/down costs a little precision but nothing is wasted.

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 two-parameter interaction tool with no output schema, it covers the action and the authorization caveat but leaves the second parameter and post-call observation behavior unexplained. An agent could call it, but could not predict the observe side effects from the description alone.

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 0%, so the description must carry parameter meaning, but it collapses volume_up/volume_down into a single 'volume' and never mentions the 'observe' parameter (none/tree/screenshot/both), which materially changes what the call returns. Only the required key is partially covered.

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?

Names a specific verb (press) plus the exact key set, and 'once' distinguishes it from a long-press or repeat action. It is clearly separable from aua_tap/aua_screen_action since it requires no coordinates, though it never states that contrast explicitly.

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?

Usage is implied ('press home/back/... once') and the note that 'Enter may submit' hints at when a press has consequences, but there is no guidance on when to pick this over aua_tap, aua_screen_action, or aua_type_text, and no stated prerequisites for the authorize step.

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