execute_streaming_command_code

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only mentions 'streaming output' without explaining how output is delivered, whether the command runs asynchronously, error handling, or any side effects. This is insufficient for a shell execution tool.

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 concise sentence that is front-loaded with the core action. It avoids unnecessary words, but its extreme brevity leaves out important behavioral details, though that is more a completeness issue than a conciseness one.

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 the tool's complexity (shell execution with streaming output) and the lack of an output schema, the description offers almost no guidance on return values, streaming semantics, or how it differs from the non-streaming sibling. This is a significant completeness gap for an agent to invoke 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 already has 100% description coverage for all three parameters (command, cwd, timeout), so the baseline is 3. The tool description does not add any additional meaning beyond what the schema provides, but it does not need to compensate for missing schema information.

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 (execute) and resource (shell commands), and the addition of 'streaming output' helps distinguish it from sibling tools like execute_shell_command_code. However, the distinction is implicit and not explicitly contrasted with 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 no guidance on when to use this tool versus alternatives such as execute_shell_command_code or run_script_code. It does not mention typical scenarios, exclusions, or why streaming output would be preferred.

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