iphone_terminate_app

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

No annotations are provided, so the description carries the full behavioral burden. It conveys that the process is ended (a destructive action) but gives no detail on what happens if the app isn't running, whether it is a hard kill or background, or any side effects on app state or user data.

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?

Two short sentences, front-loaded with the action and then the key parameter detail; no wasted wording.

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 five-parameter tool with no annotations, no output schema, and a significant 'then' chaining feature (returning elements/screenshot to save a call), the description is too thin. The core purpose is covered but the post-action chaining behavior and preconditions are left undocumented.

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 genuine meaning for the 'app' parameter (Bundle ID vs display name), which the schema leaves as a bare string. However, it says nothing about the four 'then*' chaining parameters, so it only partially compensates and relies on the 80% schema coverage for the rest.

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?

States a specific verb and resource: ending an app process, and clarifies the app parameter accepts either a Bundle ID or display name. It is clearly distinguishable from iphone_launch_app, though it doesn't explicitly name the sibling.

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 by the name and verb (terminate a running app), but there is no explicit when-to-use guidance, no mention of iphone_launch_app as the complementary tool, and no preconditions such as the app needing to be running.

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