websex_bash

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

With no annotations, the description carries the full burden and does add real behavioral context: asynchronous execution, client-cancellability, pipeline/redirection support, and the container as the trust boundary. However, it does not disclose the destructive potential of running arbitrary code, permission/auth requirements, or how output and cancellation results are surfaced.

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?

Two tight sentences with the primary action front-loaded, followed by capabilities and execution model. No filler; every clause carries information.

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?

The output schema spares the description from explaining return values, and the execution model is described. But for a five-parameter arbitrary-code-execution tool with zero annotation coverage and 0% schema descriptions, the missing parameter semantics and safety details leave notable 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 0% across five parameters, so the description should compensate, yet it only vaguely gestures at 'engagement directory' and says nothing about stdin, environment, or working_directory. The remaining parameters are undocumented in both schema and description.

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: running an arbitrary Bash script inside the WebSex container, scoped to the selected engagement directory. Clear on its own, but it never names the obvious siblings (websex_execute, websex_python), so an agent gets no differentiation among the several 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?

There is no when-to-use guidance and no reference to alternatives like websex_execute or websex_python. The 'container is the trust boundary' line is context, not routing, so the agent must infer when Bash execution is preferred over the other execution tools.

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