e2b_list_processes

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

The description implies a read-only operation by using 'list', but it does not explicitly state side effects, whether it is non-mutating, or what it returns (e.g., process details, format). Since no annotations are present, the description should cover behavioral aspects, but it only provides basic functionality.

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, concise sentence that directly states the tool's purpose without extraneous information. It is well-structured and easy to parse.

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 simplicity of the tool, the description covers the basic purpose but lacks essential context such as output format, potential errors, or parameter details. It does not fully equip an agent to use the tool correctly, especially with incomplete parameter descriptions.

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 includes parameters like sandboxId and username without descriptions, and the tool description adds no additional meaning. While port and accessToken have descriptions, the purpose of username and the role of sandboxId are not explained, leaving ambiguity. The tool description does not clarify parameter usage.

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 function: 'List running processes started via envd in a sandbox.' It is specific about the resource (processes) and the context (envd in a sandbox), allowing it to be distinguished from sibling tools like e2b_list_dir or e2b_run_command.

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 does not provide any guidance on when to use this tool versus alternatives. It lacks context such as 'use this to check running processes' or how it compares to running 'ps' via e2b_run_command. No usage scenarios or exclusions are mentioned.

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