terminate_app

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

Annotations already indicate a mutating operation (readOnlyHint=false). The description adds that the action targets a running app on the iOS Simulator, which is useful, but it does not disclose failure modes, side effects, or requirements like needing a booted simulator. It provides some value beyond annotations but lacks richer behavioral context.

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, grammatically clean sentence that promptly states the action, target, and method. No filler or repetition, earning it the highest score for conciseness.

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 simple two-parameter tool with no output schema, this description sufficiently covers the core action. It lacks mention of error handling, simulator state prerequisites, or inverse relationship with launch_app, but these are not essential for basic invocation. Minor gaps keep it from a 5.

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 fully documents both parameters with descriptions (100% coverage), so the description's mention of 'by bundle identifier' adds no new semantic detail. The baseline of 3 applies since the schema does the heavy lifting for parameter understanding.

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 the specific verb 'Terminates' with a clear resource 'a running app on the iOS Simulator' and method 'by bundle identifier'. This precisely defines the tool's function and distinguishes it from sibling tools like launch_app and install_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 description clearly implies the tool is for stopping a running app, which gives strong contextual use guidance. However, it does not explicitly mention alternatives or conditions when to avoid use, such as non-running apps or dependency on a booted simulator, missing the top benchmark.

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