execute_command_streaming

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

With no annotations, the description carries the burden. It discloses that output is collected line by line and returned as a single string, and that the command is blocked if it matches a security blacklist. However, it does not clarify side effects, blocking behavior, or whether the command runs in a sandbox, leaving gaps for an AI agent.

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 concise, with three sentences and one additional note. It front-loads the purpose, follows with intended usage, and adds a behavioral constraint. Every sentence is necessary and well-structured without redundancy.

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 presence of an output schema and context signals, the description adequately covers the tool's purpose and key constraints. It could be more explicit about when to use this over sibling tools like 'execute_command', but it provides enough context for most use cases.

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%, so the parameter descriptions already explain each parameter. The tool description adds little beyond schema; it merely reinforces what the schema says (e.g., 'Shell command to execute'). Hence, the description meets the baseline but does not provide additional value.

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 tool executes a long-running command with incremental output, distinguishing it from the sibling tool 'execute_command' which presumably returns output all at once. It specifies the resource (command) and the outcome (incremental output).

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?

It explicitly says it's intended for commands that produce output over time (builds, tests, long scripts) and mentions that true streaming requires SSE, which provides context. However, it does not explicitly state when not to use it or directly name alternative tools, leaving some ambiguity.

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