kill

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

Adds context beyond destructiveHint annotation: describes potential termination/alteration, explains dry-run preview, and safe failure mode without allow_signal.

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?

Compact paragraph with all necessary info front-loaded: main action, safety, usage, and alternatives. No superfluous sentences.

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?

Comprehensive for a signal-sending tool with no output schema: covers purpose, parameters, safety, limitations, and related tools.

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?

With 100% schema coverage, description still adds value by explaining the intent of each key parameter (e.g., 'preview' for dry_run, 'actual signal delivery' for allow_signal).

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?

Clearly states verb 'plan or send a signal' and resource 'to a process by PID', distinguishing from sibling tools like 'ps' for listing and 'nohup' for no hang-up.

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 tells when to use (signal, terminate, restart) and when not (process listing), names alternatives ('ps', 'pidof', 'nohup'), and explains safety flags (--dry_run, --allow_signal).

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