terminate_app

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

No annotations are provided, and the description does not disclose behavioral traits such as whether termination is graceful or forceful, if it triggers confirmation dialogs, or what happens to app state. The agent lacks insight into side effects or constraints beyond the obvious terminal 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?

The description is a single, clear sentence with no unnecessary words. It efficiently conveys the core purpose and platform scope, making it easy to parse quickly.

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?

Given the 3 parameters (2 required) and no output schema, the description is too minimal. It omits behavioral details, usage context, and error scenarios. The agent would need to consult other documentation or trial-and-error to use this tool reliably alongside the listed siblings.

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 description adds no additional meaning to the parameters beyond what the input schema already provides. While the schema covers 'appId' and 'deviceId' with descriptions, the 'platform' parameter is only listed via enum and has no separate description; the description does not compensate for this gap or clarify parameter relationships.

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 ('terminate'), the resource ('a mobile app'), and the context ('on Android or iOS simulator'). It effectively distinguishes this tool from sibling tools like start_app, restart_app, or stop_log_stream by specifying the exact operation and platform.

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 provided on when to use this tool versus alternatives (e.g., restart_app, press_back, or force stop via system settings). The description lacks context about prerequisites, session states, or typical use cases, leaving the agent to infer without support.

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