Open Workspace

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

Annotations already provide the safety profile (read-only, non-destructive). The description goes beyond them by detailing the workspace_id plus git status, AGENTS.md, and compact file tree that will be returned, giving the agent a concrete expectation of the response. It does not discuss potential scan costs or non-idempotent behavior, but this is minor given the parameter schema and hints.

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 short sentences carry the purpose and the output contract with no filler. The return value list is front-loaded after the verb phrase, making the core behavior immediately readable.

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?

Although there is no output schema, the description names the important returned fields. All optional parameters are documented in the schema, and the annotations cover safety concerns, so an agent has enough context to invoke the tool and interpret its result.

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 seven parameters are fully described in the schema (100% coverage), so the baseline applies. The description's mention of 'local project directory' simply echoes the path/root parameter without adding syntax or edge-case detail beyond the schema.

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 action ('Open a local project directory as a LocalWorkspaceBridge workspace') and names the key results (workspace_id plus git status, AGENTS.md, and file tree). This clearly differentiates it from siblings like open_current_workspace, which works on the current directory rather than a user-supplied root.

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?

Usage is implied: call this when you need to open a local project directory into a workspace. However, the description does not explicitly contrast it with open_current_workspace or say when to prefer one over the other, leaving the agent to infer routing.

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