Terminate multiple sandboxes at once to free resources. Bulk delete destroys each sandbox and its filesystem permanently. Use for cleanup of many sessions.
Terminate MULTIPLE sandboxes in one call (bulk). IRREVERSIBLE — every listed sandbox and its filesystem is destroyed. Use tenki_terminate_sandbox for a single one.
| Name | Required | Description | Default |
|---|---|---|---|
| session_ids | Yes | The sandbox/session IDs to terminate. |
Changes observed during successful MCP inspections.
v0.3.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, so the destructive nature is known. The description adds valuable context by stating the operation is IRREVERSIBLE and that every listed sandbox's filesystem is destroyed, going beyond the annotation.
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 sentences with no wasted words. It front-loads the core purpose, includes the critical warning, and provides the routing to the single-sandbox alternative.
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 destructive bulk operation with a single well-documented parameter, the description covers purpose, scope, irreversibility, and the alternative tool. The annotations handle the destructive hint, and the schema fully documents the parameter, so nothing essential is missing.
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 100%, with the session_ids parameter fully documented including type, format, and source. The description does not add parameter-level details, so the baseline score of 3 is appropriate.
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 a specific verb and resource: terminate multiple sandboxes in bulk. It also distinguishes itself from the sibling tenki_terminate_sandbox by explicitly noting the single-sandbox alternative.
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 gives explicit usage guidance: use this tool for bulk termination and use tenki_terminate_sandbox for a single sandbox. This makes the choice between the two tools unambiguous.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.