Close Workspace

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

Annotations already mark this as destructive, but the description goes further by warning that all documents, unsaved changes, and handles are lost, and explains that the default workspace respawns cleanly. This adds substantial behavioral context beyond the structured annotations.

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?

Every sentence in the description earns its place: action, consequences, current-workspace behavior, default-workspace behavior, and return value. It is front-loaded with the most important information and contains 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?

For a single-parameter destructive tool with no output schema, the description fully covers what happens, including side effects, special cases, and the exact return shape. Nothing needed for correct invocation is missing.

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 only provides a required string 'name' with no description. The tool description compensates by making clear the parameter refers to a workspace, and specifically notes that the current workspace and the default workspace are valid special cases. It does not list sources of valid names, but the meaning is sufficiently conveyed.

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: "Shut down a workspace's worker and free its pool slot." It clearly distinguishes this from sibling tools like close_document or use_workspace by emphasizing worker shutdown, pool slot release, and loss of workspace documents and handles.

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 for when closing is appropriate, including the behavior of closing the current workspace and the default workspace. It lacks an explicit comparison to alternatives like restart_worker, but the usage context is clear enough that an agent can select this tool appropriately.

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