e2b_delete_sandbox

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

With no annotations, the description must disclose side effects. It only says 'permanently,' which indicates non-reversibility, but doesn't mention what happens to running processes, data, or whether any cleanup occurs. It also doesn't mention if it can be called on any sandbox regardless of state.

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 a single short sentence, which is concise, but it sacrifices essential detail. It could be expanded to include parameter meaning and usage while staying compact.

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 operation with no annotations and no output schema, the description is severely incomplete. It omits parameter semantics, usage conditions, and behavioral effects, leaving the agent with insufficient information to invoke the tool safely.

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 has zero descriptions, and the description does not explain the sandboxId parameter. The agent is left to infer that the parameter identifies the sandbox, but no format, validation, or guidance is given. This fails to compensate for the 0% schema coverage.

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 the action (kill/delete) and the resource (sandbox), and the word 'permanently' signals it's a destructive operation distinct from pausing or setting timeouts. This distinguishes it from siblings like e2b_pause_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?

There is no explicit guidance on when to use this tool versus alternatives. The 'permanently' wording implies it's for final deletion, but it doesn't state when to prefer this over pausing or setting timeouts, nor any conditions like 'use after the sandbox is idle'.

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