ssh_shell_write

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

With no annotations, the description must carry the full burden of behavioral disclosure, but it only states the action 'Send a command.' It does not mention buffering behavior (such as the 'clear' flag semantics), how to retrieve output, or whether the command execution is asynchronous. This leaves significant ambiguity.

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 sentence with no unnecessary words. It is front-loaded with the essential action and target, making it highly concise and well-structured.

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?

The description is too terse for a tool with 3 parameters and no output schema. It does not explain the tool's role in the SSH shell workflow, the relationship to ssh_shell_open and ssh_shell_read, or the meaning of the buffer clearing behavior. An agent would need additional context to use it correctly.

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 input schema fully describes all three parameters with 100% coverage, including the meaning of the 'clear' flag and the session_id origin. The description adds no parameter semantics beyond what the schema already provides, so the baseline of 3 applies.

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 'Send a command to an SSH shell session' clearly states the action and target, making the core purpose unmistakable. However, it does not differentiate from sibling tools like ssh_shell_exec, which also sends commands but with different semantics, so it misses the top score.

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?

There is no guidance on when to use this tool versus alternatives such as ssh_shell_exec or ssh_shell_send_ctrl. The description lacks any mention of prerequisites (e.g., an open session) or the intended interaction model, leaving the agent without direction.

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