save_workspaces

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It clearly states side effects (flushes Drive, unmounts it), state outcome (VM stays allocated), a refusal condition (managed jobs active), and a follow-up requirement (remount Drive). This is unusually transparent for a zero-parameter tool.

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 concise and front-loaded with the primary action, followed by short sentences for state, guard condition, and post-condition. Every sentence adds distinct value and none are redundant.

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 tool with no parameters, no annotations, and no output schema, the description covers all essential context: what the tool does, what side effects it has, when it refuses, and what must happen afterward. An agent has enough information to select and invoke it correctly.

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 tool has zero parameters, so there are no parameter semantics for the description to clarify. The baseline of 4 applies, and the description reinforces that the operation is fixed-scope and requires no input.

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 names a specific verb and resource: 'Checkpoint all managed workspaces, flush Drive, and unmount it.' It also states 'VM stays allocated,' which clearly separates this from sibling tools like safe_stop or restore_workspace. The operation is unambiguous and specific.

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 usage context: it refuses to run while managed jobs are active, which tells the agent when not to call it, and it warns to remount Drive before further persistence operations. It does not explicitly name alternatives or compare this tool with restore_workspace or safe_stop, so it falls just short of full guidance.

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