Close Workspace

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

Annotation Contradiction: readOnlyHint is true, yet the description says the tool will 'Forget one opened workspace from this server session,' which is a state-changing action in the server session. This directly contradicts the read-only annotation. The clarification that it does not delete files is helpful, but the contradiction makes the behavioral transparency unreliable.

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 sentences with no wasted words. The core action is front-loaded, and the second sentence earns its place by disambiguating from file deletion.

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 tool with no nested objects or output schema, the description covers the core behavior, the session scope, and the non-destructive nature. It is adequate for an agent to invoke correctly, though the annotation contradiction prevents full completeness.

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 100% and the only parameter, workspace_id, is already described as 'Workspace id to close.' The description adds only the qualifier 'opened' to the workspace, which is mild extra context. With full schema coverage, the baseline of 3 is appropriate.

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 uses the specific verb 'Forget' with a clear resource, 'one opened workspace,' and scopes the action to 'this server session.' It also explicitly distinguishes itself from file-deleting operations by stating 'This does not delete files,' so an agent can separate it from filesystem tools and from open_workspace.

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: use this to forget one opened workspace from the current server session. It does not explicitly name alternatives or when-not-to-use conditions, but the intended use case is evident from the wording and sibling names.

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