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

With no annotations present, the description must carry the behavioral disclosure burden. It does disclose a key operational trait: no automation session is required. But it does not state that killing by PID or process name can terminate non-app processes, whether the kill is forceful, or what side effects occur, leaving meaningful behavioral gaps 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. The main capability and target selectors are front-loaded, followed by the session-requirement note. Every word adds information.

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 destructive iOS process tool with no annotations and no output schema, the description is adequate but leaves an important gap: the schema marks only `udid` as required, and the description does not clarify that at least one of `pid`, `bundleId`, or `processName` is needed, nor that they are alternatives. Simple to read, but an agent could attempt an invalid call with only a UDID.

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%, so the parameter names and their meanings are already documented. The description repeats the three target selectors without adding extra semantics such as 'exactly one of pid, bundleId, or processName must be provided,' which would have elevated the score.

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 names a specific action ('Kill'), a specific resource ('an app on an iOS device'), and the supported target selectors (bundle ID, process ID, or process name). It is clear and unambiguous, but it does not explicitly distinguish this from the similarly named sibling `ios_terminate_app`, so it misses the fifth point.

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' provides a concrete usage context: the agent can invoke this tool standalone without first establishing an iOS automation session. However, the description does not name alternatives such as `ios_terminate_app` or state when the agent should prefer one over the other, so it stops short of full when/when-not guidance.

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