Write to persistent process stdin

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

Annotations already declare readOnlyHint=false, destructiveHint=true, and openWorldHint=true, so the safety profile is covered. The description adds the environment-variable gate, which is genuine extra context, but says nothing about what the write mutates, newline handling, or irreversibility beyond what annotations imply.

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 tight sentences, front-loaded with the core action followed by the constraint. Nothing is wasted, though it is arguably too terse given the undocumented parameters.

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 destructive, open-world mutation tool with 5 parameters at 0% schema coverage and no output schema, the description is far too thin. The env-var gate is a good start, but parameter meaning, interaction with the process lifecycle, and differentiation from interact_with_process are missing.

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 0% across 5 parameters, so the description carries the full burden. It names nothing: sessionId, deviceId, deviceName, input, and appendNewline are all left to their bare types, and 'send input' does not even clarify the required 'input' semantics or the appendNewline default behavior.

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?

States a specific verb+resource: sending input to a running process session, which is distinguishable from read-side siblings like read_process_output. However, it does not differentiate itself from the near-sibling interact_with_process, leaving the agent to guess which to call.

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?

Provides a real prerequisite (RACCOON_ENABLE_SHELL=1) which is useful gating context, but gives no when-to-use vs interact_with_process guidance and no exclusions. Usage is implied rather than stated.

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