mobile_stop_current_app

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

No annotations are provided, so the description carries the burden of behavioral disclosure. It states the core destructive behavior (stopping the foreground app) and notes that the return is a JSON response, but it does not cover prerequisites, failure cases, or what the JSON response contains. It is not misleading, but it is thin.

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 very compact: one sentence plus an Args/Returns stub with no wasted words. The primary action is front-loaded, and the parameter and return information are clearly structured.

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 single-parameter command, the basic invocation is clear, but the description omits when to choose this tool over the closely related mobile_stop_app and does not address edge cases like no foreground app. The output schema mitigates the need for return details, but the tool-family context makes this only minimally complete.

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 schema only provides the parameter name and type, but the description adds meaning by explaining that serialno is the mobile device serial number and where to obtain it ('from list_devices'). This meaningfully compensates for the 0% schema description coverage.

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 states a specific action ('Stop') and a clearly targeted resource ('the app currently in the foreground'), which distinguishes it from the sibling mobile_stop_app, which would stop a named app. It does not explicitly name the alternative, but the foreground qualifier is a strong differentiator.

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 guidance is given on when to use this tool versus mobile_stop_app or mobile_current_app. The only hint is that serialno comes from list_devices, which is more about parameter sourcing than usage context. There is no mention of exclusions or alternatives.

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