kill_process

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

Annotations already indicate destructiveHint=true; description adds value by explaining the two-step graceful-then-force behavior and warns about data loss. No contradictions.

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?

Very concise: 5 sentences. Each sentence contributes: purpose, parameter guidance, behavior, warning, and return type. Well-structured and easy to scan.

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?

Covers all essential aspects: what it does, how to use it (two parameters alternatives), destructive nature, and return format. Output schema exists, so description doesn't need to elaborate on results. Complete for an agent.

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 descriptions cover all parameters (100% coverage), but the tool description adds nuance (preferred pid, kill hard vs graceful). Baseline 3 with high schema coverage, and description provides moderate additional context.

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?

Clear verb and resource ('Kill a process'), specifying two methods (by PID or exact name), which distinguishes it from sibling tools like list_processes. No ambiguity.

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?

Explicitly states to provide 'pid' (preferred) or 'name', and describes the force flag usage. Lacks explicit when-not-to-use, but the context is sufficient for typical process killing tasks.

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