e2b_close_stdin

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

With no annotations, the description carries the burden of explaining behavior. It does clearly say that the operation sends EOF, which is meaningful. It does not, however, disclose potential side effects such as the process exiting or how the operation behaves if stdin is already closed.

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 well-structured sentence, with the key action and target front-loaded. Every part earns its place, and there is no redundant or filler wording.

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 six parameters, no annotations, no output schema, and partial schema descriptions, the tool definition is not complete enough. It omits important calling context such as whether pid or tag is required, mutual exclusivity, authentication considerations, and expected success/error behavior.

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 description adds value by clarifying that 'pid or tag' selects the process, which is not clear from the schema alone. However, schema coverage is only 50%, and the description does not explain username, accessToken, or the relationship/optionality between pid and tag.

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 action ('Close stdin (send EOF)') and the target resource ('non-PTY process running in a sandbox'), with a selection method ('by pid or tag'). It is specific and understandable, though it does not explicitly name sibling alternatives.

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 provides useful context about when this tool applies: it is for non-PTY processes and selects by pid or tag. However, it does not explicitly contrast with related tools like e2b_send_stdin or state when not to use it, so usage guidance is mostly implied.

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