Launch workspace

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

With no annotations, the description takes on the burden of disclosure. It reveals important behavioral traits: the launcher must be supplied or set via HYPERPANES_BIN, the default mode writes a temp file, and cli mode drops JSON-only fields. It does not mention return values or blocking behavior, but the disclosed details are substantive.

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 sentences pack a wealth of actionable detail: purpose, input alternatives, launcher requirement, environment variable, default mode, and tradeoffs. No word is wasted, and the most critical information is 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?

Given the tool has no output schema or annotations, the description covers the essential inputs, launcher setup, and mode semantics well. It lacks explicit post-launch behavior or error cases, but for a tool of this complexity the description is largely sufficient.

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?

The schema covers path, mode, and launcher, but the spec parameter is empty. The description compensates by explaining spec is a workspace object, and it adds meaning to mode by describing default behavior and data loss implications. This exceeds the schema-only baseline.

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 launches hyperpanes with a workspace, using a specific verb and resource. It distinguishes itself from siblings like build_workspace and validate_workspace by focusing on the launch action and detailing the input options (path or spec).

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 provides clear context on how to use the tool: provide a path or spec, and require a launcher via parameter or environment variable. It also explains the two modes and their tradeoffs, though it does not explicitly name alternative tools or when not to use it.

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