Terminate an app

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

The description discloses that the tool only affects running apps and explicitly says it does not uninstall or reset state, which is useful non-destructive context. However, with no annotations, it omits what happens if the app is not running, whether a booted simulator is required, or any error behavior, leaving the agent to guess.

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?

A single sentence that front-loads the action and immediately clarifies what the tool does not do. There is no filler; every phrase contributes meaning, making it easy to scan and understand.

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 two-parameter mutation tool with no annotations and no output schema, the description covers the core action and the key non-effect. It lacks failure-mode details and prerequisites (e.g., simulator must be booted, app must be installed), but for such a simple tool these gaps are minor.

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 covers 'udid' with a description, but 'bundleId' has none. The description's phrase 'by bundle identifier' merely echoes the parameter name and adds no format, examples, or validation. Since schema description coverage is only 50%, the description should compensate for the undocumented bundleId parameter, but it doesn't.

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 verb ('Terminate'), a specific resource ('running simulator app'), and the method ('by bundle identifier'). It explicitly differentiates itself by noting what it does NOT do ('without uninstalling it or resetting its state'), which helps distinguish from sibling actions like install_app or launch_app.

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?

The phrase 'without uninstalling it or resetting its state' gives a clear usage boundary: use this when you want to stop an app but preserve its data. It does not name alternative tools explicitly, but the context is strong enough that an agent can infer when to choose this over other simulator commands.

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