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

Annotations already declare destructiveHint=true, idempotentHint=true and readOnlyHint=false, so the safety profile is covered. The description usefully adds the session prerequisite and the default-target behavior, but says nothing about whether app data/state is preserved, which is the key behavioral question separating terminate from clear-data tools.

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?

Three short sentences, zero filler, with the core action first and the default behavior and precondition following. Every sentence carries information an agent needs.

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 and full annotation coverage, the description supplies purpose, default, and prerequisite. The only real gap is sibling differentiation against ios_kill_app, which matters given how many overlapping terminate/kill tools exist.

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 description coverage is 100% and both parameters are documented there, including the exact 'default: current foreground app' note the description repeats. The description adds no syntax, format, or resolution detail beyond the schema, so the baseline 3 applies.

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?

Names a specific verb and resource ('Terminate an app on an iOS device'), which is clearer than the bare title. However, it makes no attempt to distinguish itself from near-identical siblings like ios_kill_app and device_terminate_app, so an agent cannot route between them from this text alone.

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?

It states the precondition ('Requires an active iOS automation session') and the fallback behavior when bundleId is omitted, which is genuine usage context. It gives no guidance on when to prefer this over ios_kill_app or device_terminate_app, so the choice among overlapping terminate tools is left to inference.

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