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

Annotations already declare destructiveHint=true, idempotentHint=true, readOnlyHint=false and openWorldHint=false, so the safety profile is covered. The description adds the useful session-independence fact, but says nothing about impact on app data, whether a running session is disrupted, or what happens if the identifier matches nothing — a meaningful gap for a destructive operation.

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, zero filler, and the core action plus its accepted identifiers are front-loaded ahead of the session note. Nothing needs trimming.

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?

With no output schema and full annotation/schema coverage, the description covers the basics for a destructive one-shot call. What it omits is the disambiguation from ios_terminate_app and any note on failure modes, which an agent selecting among ~250 siblings would likely need.

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 all four parameters (pid, udid, bundleId, processName) are documented in the schema, so the baseline is 3. The description restates the three identifier options but adds no precedence rules, mutual-exclusion constraints, or format details beyond the schema.

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 (kill), resource (an app on an iOS device), and the three accepted identifiers (bundle ID, process ID, process name), so the action is unambiguous. However, it does not distinguish itself from the closely-named sibling ios_terminate_app (or device_terminate_app), which appears to do the same thing — an agent cannot tell them apart 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?

'No automation session required' gives one clear precondition for use, which is real guidance. But there is no statement of when to prefer this over ios_terminate_app, nor what to do if multiple identifiers are supplied or the app is already dead. Usage is implied rather than spelled out.

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