exec_stream

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

There are no annotations, so the description carries the full burden of behavioral disclosure. It only mentions 'streaming output collection' but does not explain whether the command blocks, how output is delivered, what happens on timeout, or the exit code behavior. This is minimal information and does not adequately prepare the agent for invocation.

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 extremely short and front-loaded, but it is under-specified. It lacks essential information about scope, behavior, and parameter semantics, making it insufficient for safe and correct use. This is not 'appropriately sized' but rather an overly terse description that fails its purpose.

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 simplicity of the tool (2 parameters, no output schema), a one-sentence description could theoretically be sufficient if it included key context. However, with many sibling execution tools and no annotations, the description is incomplete. It does not clarify execution environment, output handling, or relationship to other tools, leaving the agent under-informed.

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 0%, so the description must compensate. It does not explain the 'command' or 'timeout' parameters beyond their obvious names, providing no additional context such as format, units, or constraints. The parameter names are mildly self-explanatory, but the description adds no value to the schema.

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 states a specific verb ('Execute') and a resource ('a command'), but it fails to indicate where the command executes (local vs. remote) or how this differs from sibling tools like kali_exec or ssh_session_command. The 'streaming output collection' detail is vague and does not sufficiently distinguish it from other execution tools.

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 guidance is provided on when to use exec_stream versus alternatives. The description does not mention any exclusions, prerequisites, or specific use cases, leaving the agent to infer from the name alone. This is a significant gap given the large number of sibling exec-related tools.

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