app_launch

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

With no annotations, the description carries the full burden. It discloses key behaviors: skips UI navigation, fails on active app or unknown name, args as file path, then_screenshot default. Occasional vagueness ('Real action.') prevents 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?

Description is concise (4 sentences) and front-loaded with the main action. The phrase 'Real action.' is slightly redundant but not detrimental. Efficient overall.

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?

Despite no output schema and 3 parameters, the description covers behavior, constraints, parameter details, and failure modes. It is complete enough for an agent to use correctly.

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%, so the description compensates fully. It explains 'name' as exact app name with examples, 'args' as optional file path, and 'then_screenshot' defaulting to True. Provides clear semantics 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 tool's purpose: 'Launch a Flipper app BY NAME over BLE (app_start_request) — skips UI navigation.' It uses a specific verb ('Launch'), resource ('app'), and distinguishes from sibling tools like app_exit and app_button.

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?

Explicit guidance: 'FAILS if an app is already running (app_exit first) or the name is unknown.' Also advises to get exact names from the app_list, providing clear when-to-use and exclusions.

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