Force terminate managed process

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

Annotations already declare destructiveHint=true, readOnlyHint=false, and openWorldHint=false, so the safety profile is covered. The description adds the useful scoping fact that the target is a Raccoon-managed persistent process, but it does not explain what 'force' means (SIGKILL vs. graceful signal), whether buffered output is lost, or whether the process must be currently running.

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 front-loaded sentence with zero filler and no redundant restatement of the title. Its terseness is arguably the flaw, but it is not padded or poorly structured.

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, 3-parameter mutation tool with 0% schema coverage, no output schema, and multiple competing kill/stop siblings, the description is too thin. It omits force-vs-graceful semantics, required process identity beyond a bare pid, and any indication of failure modes when the pid is not Raccoon-managed.

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 0% across 3 parameters, so the description carries the full burden and does not compensate: it never mentions pid, deviceId, or deviceName, nor how to disambiguate a process on one device versus another. It only implies that some process identifier is the target.

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 (Terminate) and resource (persistent process) and narrows the scope with 'started through Raccoon', which implicitly separates it from generic OS-level killers. However, the sibling set contains kill_process, process_kill, and stop_search, and the description never explicitly contrasts itself with them, so an agent must infer the difference.

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 when-to-use guidance at all, despite several overlapping termination/stop siblings (kill_process, process_kill, stop_search). Nothing states the precondition that the process must be one tracked by Raccoon, nor when force termination is preferable to a graceful stop.

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