layerfs_workspace_exec

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

Beyond the annotations, the description discloses important behavior: output includes complete stdout/stderr and exitCode, the command does not checkpoint state, and a client timeout does not prove the command stopped. This adds meaningful operational context about side effects and retry safety, though it does not mention permissions or concurrency limits.

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 three tight sentences, front-loaded with what the tool does and followed by critical operational caveats. Every sentence carries useful information with no filler.

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 description covers return values, checkpointing behavior, and timeout retry safety, which is useful given the destructive and open-world annotations. However, it leaves the caller without guidance on the nested workspace parameter structure, a notable gap for a tool with no parameter descriptions and no 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 description coverage is 0%, and the description provides no explanation of the three parameters, including the nested workspace object fields (sandbox, path, image) or the message field. It implies a ws and command are needed but does not compensate for the missing schema documentation.

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 and resource: 'Run a command in a mounted Workspace,' and notes that it returns stdout/stderr and exitCode. It clearly identifies the core operation, though it does not explicitly differentiate this tool from sibling process-management tools such as process_start.

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 gives concrete post-execution workflow guidance: call workspace.commit afterward, including after a failing command, and inspect before retrying after a client timeout. It stops short of explaining when to choose this tool over process_start or other siblings for background or long-running commands.

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