e2b_refresh_sandbox

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

With no annotations available, the description carries the full burden. It does disclose the core behavioral effect: extending the sandbox's time to live. However, it leaves key behavior implicit, such as what happens when duration is omitted and whether the operation has side effects beyond refreshing the TTL.

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 one short sentence that gets straight to the purpose and effect. No waste and the core idea is front-loaded.

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 2-parameter tool with no annotations and no output schema, the description is sparse. It omits the distinction from e2b_set_sandbox_timeout, doesn't explain what happens if duration is omitted, and provides no sense of expected behavior when the sandbox is already expired.

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 coverage is 50% with sandboxId undocumented, and the description adds little beyond the schema. 'Extending its time to live' maps to the duration parameter, but the description does not clarify the exact relationship between duration, the refresh action, or any default behavior for omitted duration.

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 uses a clear verb-resource pair ('Refresh a sandbox') and states the primary effect ('extending its time to live'). However, it does not explicitly distinguish itself from the sibling e2b_set_sandbox_timeout, which may cover an overlapping use case.

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 guidance on when to use this tool instead of e2b_set_sandbox_timeout or any other alternative. The description states only what the tool does, not the context or conditions that should prompt an agent to call it.

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