sandbox_create

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

With no annotations, description partially discloses behavior: creates a VM, returns sandboxId. Does not mention cost, resource limits, or security implications.

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 concise sentences, front-loaded with key action and return value, no wasted words.

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 3 optional params with full schema coverage and no output schema, the description is adequate but leaves out return format details and cost implications.

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 has 100% coverage, so parameters are well-documented. The description does not add meaning beyond schema defaults and max values.

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 it creates a new E2B cloud sandbox (secure Linux VM) and returns a sandboxId. It distinguishes itself from sibling tools which are operations on existing sandboxes.

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 implies this is the first tool to use (since it returns sandboxId used by others), but does not explicitly state when to use vs alternatives. Among siblings, it's the creation tool.

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