Manage a temporary artist workspace

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

Beyond the annotations (readOnlyHint=false, openWorldHint=true, destructiveHint=false), the description reveals important behavioral traits: main-thread scheduling, JSON-only job state, compare-and-swap restoration, fail-closed behavior in Perform/headless/conflicted states, and strict no-fallback to raw Python. These give the agent a precise safety and execution model that annotations alone do not provide.

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 dense sentences deliver all essential information without redundancy. The first sentence front-loads the action and resource, and the second adds safety and constraint details. Every clause earns its place.

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?

For a 7-parameter tool with an output schema, the description covers the operational lifecycle, threading model, state handling, and security constraints. It is sufficiently complete to guide correct invocation and understand the tool's boundaries, even without re-explaining return values (covered by output schema).

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 covers 71% of parameters. The description enriches parameter understanding by explaining the bridge architecture (bounded workspace, right-hand split, compare-and-swap cleanup) which informs how split_ratio, viewer_mode, network_path, and lease_seconds fit together. It adds context beyond the schema's individual descriptions, though it does not detail every parameter.

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 clear compound verb (open, inspect, restore, or cancel) targeting a specific resource: a bounded TouchDesigner editor workspace built on an existing Network Editor plus a TOP Viewer or Panel split. This distinguishes it from create/delete siblings and specifies exact scope.

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?

The description gives clear context: this tool is for managing one temporary workspace using an existing Network Editor and a right-hand viewer/panel split. It implies when to use it (when you need a bounded, structured workspace) and describes constraints like ALLOW_EXEC=0, but does not explicitly name alternatives or state 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.