flipper_app_exit

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It clearly states the action and outcome, but does not mention edge cases (e.g., no app running, exit failure) or any side effects. This is adequate for a simple action but leaves some uncertainty.

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?

The description is a single, front-loaded sentence that directly states the tool's purpose and effect. Every word earns its place, with no filler or redundant information.

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 zero-parameter, simple action with an output schema available, the description sufficiently covers the essential context: what the tool does and the expected outcome. It could mention preconditions (like an app needing to be running) but overall it is complete for its simplicity.

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?

The input schema has zero parameters, so parameter semantics are not applicable. Per the rubric, a no-parameter tool gets a baseline of 4 because no additional parameter documentation is needed.

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 uses a specific verb ('exit') and identifies the exact resource ('the currently running app'), with a clear outcome ('returning to the desktop'). It distinguishes itself from sibling tools like flipper_app_start and flipper_reboot by describing a targeted app-level exit rather than a system reboot.

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: use when you want the currently running app to exit and return to the desktop. However, the description does not explicitly mention when not to use it (e.g., if no app is running) or compare it to alternatives like reboot, though the context makes the primary scenario clear.

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