Set Default Workspace

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

The description says the tool 'Set[s]' a workspace as default/active, which implies a state change. This directly contradicts the annotation readOnlyHint=true, which indicates the tool does not modify state. Therefore the description contradicts the 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?

The description is a single, front-loaded sentence with no filler. Every part contributes meaning: the target workspace, the precondition that it is already opened, and the effect on omitted workspace_id calls.

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 one-parameter tool, the core effect is stated, but the contradiction with readOnlyHint leaves the behavioral profile unreliable. The description also does not clarify persistence, session scope, or whether this changes any stored server state.

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 schema already explains that workspace_id comes from open_workspace/list_workspaces. The tool description adds no additional parameter semantics beyond the schema, so the baseline 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 states a specific verb ('Set'), a specific resource ('an already-opened workspace'), and the exact purpose ('default and active workspace for omitted workspace_id calls'). The phrase 'already-opened' also distinguishes it from open_workspace, which actually opens a 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 implies when to use it: after a workspace is already opened and when you want it to be the default for calls that omit workspace_id. However, it does not explicitly mention alternatives like list_workspaces/open_workspace or state when not to use the tool.

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