e2b_send_stdin

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

No annotations are present, so the description carries the full burden. It discloses a schema-reliability caveat ('field names are inferred... check the E2B docs'), which is useful. However, it does not describe effects on the process, whether a newline is appended, what happens if the process is not found, or success/error behavior.

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 core functionality is front-loaded in a single concise sentence, with a helpful caveat appended as a second sentence. No wasted words, though the caveat could be slightly shorter.

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 7-parameter tool with no annotations, no output schema, and a schema-reliability warning, the description is thin. It lacks guidance on how the tool behaves on success/failure, how to choose pid vs tag, and what the response looks like. The caveat helps, but the overall picture is incomplete.

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 description coverage is 57%, so the schema provides some parameter descriptions (port, input, sandboxId, accessToken). The description adds semantic context that pid and tag are alternative selectors, but does not clarify their mutual exclusivity or the roles of username/accessToken. Overall it adds some value but does not compensate for the undocumented parameters.

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 ('send'), the resource ('stdin of a running process'), and the selection mechanism ('by pid or tag'). This is specific enough to distinguish it from siblings like e2b_send_signal and e2b_close_stdin without needing to inspect their schemas.

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?

It implies the tool is for interacting with running processes by pid or tag, but does not explicitly state when to use it over alternatives such as e2b_close_stdin for EOF or e2b_send_signal for signals. No conditions or exclusions are provided, leaving the agent to infer the right context.

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