kill_process

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

No annotations are provided, so the description must cover behavioral traits. It states the action and default signal, but fails to mention that sending a signal can terminate processes, cause data loss, or require elevated permissions. The 'Gated' hint is vague.

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 very short (one sentence plus 'Gated'), which is efficient. However, it could be better structured with explicit sections like action, resource, and constraints.

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 simplicity and the existence of an output schema (not shown), the description should still cover side effects (process termination), error handling, and signal format specifics. It lacks completeness in these areas.

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 mentions 'PID' and 'default SIGTERM', adding context to the pid and signal parameters, but does not explain valid signal names or formats, nor that pid is required.

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 clearly states the action ('Send a signal') and the resource ('a PID'), with specifics like default SIGTERM. It distinguishes from siblings like find_processes and get_process_info, which are informational, while this tool is about signaling processes.

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 only mentions it is 'Gated,' implying access control, but provides no guidance on when to use this tool vs alternatives (e.g., when to use kill_process vs other process tools), nor any when-not-to-use conditions.

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