tmux_stream_send

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

Explains that errors from tmux are raised and that output from commands appears as %output events via tmux_stream_read. However, it does not disclose potential side effects or whether the command can be destructive, leaving ambiguity about 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?

Concise at 4 sentences with a clear front-loaded purpose. No redundant information, but could be more structured (e.g., bullet points for params).

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?

Mentions return format and error handling but lacks prerequisites (e.g., needing an active stream) and does not relate to sibling stream tools or explain integration with tmux_stream_read and tmux_stream_start.

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?

With 0% schema description coverage, the description must add meaning. It explains the 'command' parameter with an example but does not elaborate on 'stream_id' (how to obtain or format it) or 'timeout' (no explanation of its purpose or effect).

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?

Clearly states it runs a tmux command over a stream's control connection, specifying that the command is a tmux command line without the 'tmux' prefix and giving an example. This distinguishes it from other tmux tools like tmux_command which may not use streams.

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?

Implies usage within a stream context but does not explicitly state when to use this tool over alternatives like tmux_command or tmux_send_keys. No when-not-to-use or alternative tool names are provided.

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