switch_workspace

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

With no annotations, the description carries full burden but provides minimal behavioral detail. It mentions the tool affects 'subsequent operations', hinting at stateful context switching, but doesn't disclose persistence scope (session vs. request), error conditions, or side effects. More context on how this interacts with other tools would be helpful.

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?

Extremely concise with one clear sentence and a helpful parenthetical. Every word earns its place by defining the action, target, and effect without redundancy or fluff.

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 stateful context-switching tool with no annotations or output schema, the description is minimal but functional. It covers the core purpose and effect, but lacks details on behavioral implications, error handling, or integration with sibling tools, leaving gaps for an agent to infer usage.

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%, so the schema fully documents the single 'workspaceId' parameter. The description adds no additional parameter semantics beyond implying the ID is used for context switching, aligning with the baseline for high schema coverage.

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 clearly states the action ('switch context') and target resource ('to a different workspace'), with the parenthetical clarifying it affects 'subsequent operations'. It distinguishes from siblings like 'get_workspace' (read) or 'create_workspace' (write), but doesn't explicitly contrast with all workspace-related tools.

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 usage when needing to change workspace context for future actions, but doesn't specify when to use this versus alternatives like 'get_default_workspace' or direct workspace parameters in other tools. No explicit exclusions or prerequisites are mentioned.

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