ios_terminate_app

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

Annotations already declare readOnlyHint=false and idempotentHint=false, and the description adds no meaningful behavioral detail beyond the word 'force-quit.' It does not mention potential loss of unsaved state, behavior on already-terminated apps, or side effects. The description carries little weight beyond the annotations.

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 one short sentence with no fluff, and it is front-loaded with the core action. It is appropriately brief for such a simple tool, though it sacrifices substance for brevity.

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 low complexity, single parameter, complete schema coverage, and present output schema, the sparse description is nearly sufficient to invoke the tool correctly. However, it lacks usage context, error conditions, or any note about consequences, leaving the agent to rely on annotations and inference.

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?

Schema coverage is 100% and the single bundle_id parameter is well documented in the schema, so the description does not need to add parameter details. The description also provides no additional parameter context, matching the baseline for fully covered schemas.

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 'Force-quit an app' clearly identifies a specific verb and resource, making it unmistakably different from tools like ios_launch_app or ios_halt. It does not explicitly distinguish itself from siblings, but the action and target are unambiguous.

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?

There is no guidance on when to use this tool versus alternatives, nor any conditions or exclusions. An eggent must infer from the tool name and siblings that this is for terminating an app; no context is provided.

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