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

With no annotations, the description carries the full burden. It honestly discloses the WebSocket lifecycle, one-shot execution, and lack of state persistence. It does not discuss potential side effects or safety/approval requirements, but the core runtime behavior is transparent.

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?

Three focused sentences with no fluff. The most important differentiators—fresh connection, no state carryover, and intended use case—are front-loaded.

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?

Provides enough context for selecting and invoking the tool: one-shot execution, no session persistence, suitable for long-running commands. Minor gap: it does not explicitly name the session-based sibling tool, but 'session-based execution' is a clear reference.

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 descriptions cover 100% of parameters, so baseline is 3. The description adds context about workspace_id needing explicit passing when HW_WORKSPACE_ID is unset, but otherwise does not significantly enrich parameter meaning beyond 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?

Clearly states the verb (execute), resource (workspace terminal), and key behavior (fresh connection per call). Distinguishes itself from session-based execution by noting no session state carries over.

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?

Explicitly recommends use for long-running build/deploy/install commands (>30s) that do not need shell state persistence, and contrasts with session-based execution. Provides a clear decision rule for when this tool is preferred.

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