docker_exec_kill

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

With no annotations provided, the description must carry the transparency burden. It discloses the target background job and optional cleanup, but omits behavioral details like the signal being sent to the process group, the default SIGTERM, or that cleanup permanently removes the log directory. This leaves gaps about the tool's full effects.

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 two concise sentences, front-loaded with the primary action and followed by the optional cleanup. Every word earns its place, with no redundancy or filler.

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 simple tool with 3 well-documented params and no output schema, the description covers the key prerequisite (background job from docker_exec background=true) and the optional cleanup. It does not mention return values or error behavior, but these are not critical for a control operation like signaling a job.

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 provides 100% description coverage for all three parameters, so the baseline is 3. The description adds little beyond what the schema already states (e.g., the cleanup option), and repeats the context for job_id without additional semantic enrichment.

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?

Description clearly states a specific action ('Send a signal') targeting a specific resource ('background job started with docker_exec background=true'), and the optional cleanup. This distinguishes it from sibling tools like docker_exec (starting jobs) and docker_exec_result (retrieving output), making the purpose unambiguous.

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?

Provides clear context by specifying it applies to background jobs launched with docker_exec background=true. However, it does not explicitly state when not to use this tool or name alternative tools for interactive sessions, so it stops short of full guidance.

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