sandbox_process_kill

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

Description indicates a destructive action (kill process) but lacks details on side effects (e.g., orphaned processes, resource cleanup) or permission requirements. No annotations to rely on, so the description should provide more behavioral context.

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?

Two sentences with no filler. The first sentence states the action and target, the second provides a critical usage hint. Every word earns its place.

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 simple tool (two required params, no output schema), the description is mostly sufficient. It lacks details on what happens on success/failure (e.g., error codes), but that is acceptable for a straightforward kill operation.

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?

Input schema already covers both parameters with descriptions, and the description reinforces that pid comes from sandbox_process_list. With 100% schema coverage, the description adds value by clarifying the relationship between tools.

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 the verb (Kill), resource (a running process in a sandbox), and the required identifier (PID). Distinguishes from siblings like sandbox_process_list or sandbox_kill by focusing on a specific process within a sandbox.

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 where to obtain the PID by referencing sandbox_process_list, which is a key usage hint. However, it does not mention when not to use this tool (e.g., if process is part of a group kill scenario) or alternatives beyond the list command.

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