sandbox_list

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

No annotations provided, so description must convey behavioral traits. It only states it lists active sandboxes; does not mention that it returns sandbox IDs or what happens if no sandboxes exist. Lacks details on pagination or filtering, but given zero parameters, listing is straightforward.

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?

Single sentence, no waste, front-loaded with key information. Ideal conciseness for a zero-parameter list tool.

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 zero parameters and no output schema, the description is sufficient for the tool's simplicity. However, it could mention that it returns sandbox identifiers (e.g., IDs) or use cases, but not critical.

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?

Zero parameters, schema coverage 100%, so description need not add param info. Description confirms no input required, which is consistent with schema.

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?

Description clearly states verb 'list' and resource 'active E2B sandboxes managed by this server', distinguishing this tool from siblings like sandbox_info (single sandbox details) and sandbox_kill (terminate sandbox). It specifies scope: 'active' and 'managed by this server'.

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?

Description implies usage for listing active sandboxes but provides no guidance on when to use this instead of sandbox_info or sandbox_exec. No explicit exclusions or alternatives mentioned. However, with zero parameters, the usage is self-evident.

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