kill_process

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

No annotations are provided, so the description alone must disclose behavioral traits. It states the action is a 'force terminate', implying it kills without saving, but fails to mention permission requirements, error handling (e.g., missing PID), or potential side effects like data loss.

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?

The description is a single sentence of five words, containing no filler or redundancy. It is appropriately minimal for a simple action.

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?

Given the tool's destructive nature and lack of output schema, the description is incomplete. It does not explain return behavior, success indications, or what happens when the process does not exist or cannot be killed. More detail is needed for safe usage.

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?

The schema coverage is 0%, meaning the description must add value beyond the schema. The description mentions 'by PID', which clarifies that the 'pid' parameter is the process ID. This adds some meaning, but it does not explain constraints (e.g., must be positive integer, maximum value) or how to obtain a PID.

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 uses the specific verb 'Force terminate' and identifies the resource 'a process by PID'. It is clear in its action, though it does not differentiate from the sibling tool 'close_application', which may also terminate processes but by application name.

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?

The description provides no guidance on when to use this tool versus alternatives like 'close_application' for graceful shutdown or 'spawn_process' for starting processes. There is no mention of prerequisites or scenarios to avoid.

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