create_sandbox

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

With no annotations provided, the description carries full burden for behavioral disclosure. It fails to mention that creating a sandbox likely starts a new environment, consumes resources, or has limitations (e.g., concurrency). The description gives no hint about side effects, permissions, or lifecycle.

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, efficient sentence that conveys the core action without unnecessary words. It is front-loaded and clear, though it could benefit from a bit more context without losing conciseness.

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 tool has no output schema, no annotations, and 2 parameters, the description is too minimal. It does not explain what the tool returns (e.g., a sandbox ID) or any post-creation steps. Competing tools like cleanup_sandbox hint at a lifecycle that is not addressed.

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 input schema covers both parameters (resolution, timeout) with descriptions. The tool description adds no extra meaning beyond the schema; for high schema coverage, the baseline is 3. The schema descriptions are concise but sufficient.

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 verb 'Create' and the resource 'E2B desktop sandbox instance', making the tool's purpose straightforward. It is distinct from sibling tools like cleanup_sandbox or list_sandboxes, which have different actions. However, it lacks a brief explanation of what a sandbox instance is, which could help new users.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., list_sandboxes to check existing instances). There is no mention of prerequisites, such as needing an existing sandbox or authentication, or when it is appropriate to create a new sandbox.

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