press

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

No annotations provided, so description carries full burden. It mentions injecting a button and optional screenshot, but lacks details on side effects, permissions, or destructive nature. The last sentence about 'Claude Desktop prompts' is unclear and adds noise.

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?

Front-loaded with purpose, but includes a vague final sentence that could be removed. Otherwise concise for the information provided.

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?

Covers all three parameters adequately, but lacks explanation of output (e.g., how screenshot is returned) and error states. No cross-reference to sibling tools like 'screenshot'.

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 0%, but the description fully enumerates allowed values for 'button' (up|down|left|right|ok|back), 'kind' (short|long|press|release, default short), and explains 'then_screenshot' with default and behavior. This adds critical meaning beyond the schema.

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 clearly states the action ('Inject a UI button over BLE') and the resource ('drive the Flipper wirelessly'). Lists specific button values, distinguishing from sibling 'press_sequence' which handles sequences.

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?

No explicit guidance on when to use this tool vs alternatives like 'press_sequence'. No conditions, exclusions, or prerequisites mentioned.

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