execute_with_streaming

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

With no annotations, the description carries the full behavioral burden, and it delivers little: it says output streams in real time but not whether the call blocks until completion, what happens to partial output when max_duration is hit, whether the command runs in a shell, or what safety/permission posture applies to arbitrary command execution. Only the streaming trait is disclosed.

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?

A single front-loaded sentence with the core capability first and the use case second; nothing is wasted. It is, however, terse to the point of under-specification for a tool that runs arbitrary commands.

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?

Four parameters, no annotations, and no output schema, yet the description says nothing about what comes back — output format, whether exit status/errors are included, or how streamed chunks are surfaced. For a command-execution tool with zero structured support for behavior or returns, this leaves material gaps.

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 100%, including defaults for max_duration and update_interval, so the schema already does the work. The description adds nothing about parameter interplay (e.g., how update_interval interacts with streaming granularity), so the baseline 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?

States a specific verb and resource ('Execute a command') plus the distinguishing capability ('real-time output streaming'). It implicitly separates itself from execute_command and get_command_output via the streaming qualifier, but never names the sibling it differs from, so an agent must infer the distinction.

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?

'ideal for long-running builds' hints at the usage context, but there are no explicit when-not conditions and no alternatives named despite many siblings (execute_command, execute_with_auto_retrieve, get_command_output) that an agent must choose between. Usage is implied rather than directed.

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