Execute Streaming Command

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

Describes streaming output, but does not disclose side effects, permissions, or that it requires an active SSH session. Annotations provide readOnlyHint and destructiveHint, reducing burden, but description adds little beyond the name.

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?

Single clear sentence, no wasted words. Perfectly concise.

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?

Description is minimal; lacks context about prerequisites (e.g., active SSH session from ssh_open_session), behavior on timeout, or output format. Output schema exists but description could elaborate on streaming semantics.

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 coverage is 100%, so parameter details are fully in the schema. Description adds no extra meaning or context to 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?

Clearly states it executes a command and returns streaming output chunks. Distinguishes from sibling proc_exec by specifying streaming nature.

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?

No explicit when-to-use or alternatives. The term 'streaming' implies use for long-running commands, but no mention of when not to use or comparison with proc_exec.

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