Open Current Workspace

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is clear. The description adds that it targets the 'configured default workspace' without a path, but does not cover return behavior or side effects. Given annotation coverage, the description carries sufficient but not extra-rich behavioral context.

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 zero wasted words. The critical usage direction is front-loaded, and the sibling exclusion is clearly stated. Very efficient.

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?

Complete for a simple, parameterless-required tool with annotations covering safety and schema covering all optional parameters. The description covers usage timing and sibling differentiation. A minor gap is that 'configured default workspace' is not elaborated, but that is not essential for correct invocation.

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?

All four parameters have schema descriptions (100% coverage), so the description does not need to explain them. The baseline of 3 applies because the schema fully documents parameters; the description adds no additional parameter context, which is acceptable.

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 the specific action (open the configured default workspace) and explicitly distinguishes it from the sibling `open_workspace` by noting it does not accept a path. This makes the purpose unmistakable.

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?

It provides explicit timing ('once at the start') and an exclusion ('Do not call open_workspace after this unless switching roots'), directly guiding the agent on when and when not to use it relative to an alternative.

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