process_kill

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the target is a process *group* rather than a single PID, but it omits the destructive/irreversible nature of the operation, that SIGKILL cannot be caught, the default signal, and any permission requirements.

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 waste; the resource and signals come first and the scope qualifier follows. Nothing extraneous.

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 process-termination tool with no annotations, no output schema, and 0% parameter coverage, the description is too thin. It should at minimum clarify signal semantics, default behavior, and irreversibility to let an agent invoke it safely.

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%, so the description must compensate. It merely restates the three enum values with no added meaning (no graceful-vs-force semantics, no default explanation), and gives no detail on the processId beyond the process_start linkage.

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 pairs a specific verb ('Send') with a precise resource ('SIGTERM, SIGINT, or SIGKILL') and scopes the target to a process group 'started by process_start', which distinguishes it from a generic kill. It clearly conveys what the tool does, though sibling differentiation is implicit rather than stated.

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?

Usage is implied: kill a process you launched via process_start. However, there is no explicit when-to-use vs. alternative, and no guidance on which signal to pick in which situation (e.g., graceful vs. forced termination), which would be the most valuable guidance for this tool.

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