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

Since no annotations are provided, the description carries the full burden. It discloses the key behavior: clearing a bind, the effect on subsequent calls (fallback to next precedence), and what is NOT affected (path-bound mounts and OAuth token default). This is substantial and goes beyond a simple 'clears a bind.' It does not mention side effects like reversal or permissions, but the core behavior is well-transparent.

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 two sentences with no fluff. The primary action is front-loaded, and the second sentence adds essential clarifications about precedence and exclusions. Every sentence earns its place.

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 tool with only two optional parameters, full schema coverage, and an output schema present, the description is complete. It explains the effect on precedence and what is not changed, giving an agent all necessary context to invoke it correctly without requiring additional knowledge.

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 both parameters (scope and workspace) already have detailed descriptions. The tool description adds no extra parameter-specific syntax or format details, but it does reference 'conversation or workspace' which aligns with scope. Since the schema covers the parameters, 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 clearly states the action ('Clear a conversation or workspace org bind') and the scope ('for this MCP session'). It is specific about the resource and distinguishes from sibling tools like org_bind (which would set) and org_context_get (which reads) by focusing on the clearing action.

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 provides clear context for when to use the tool: to remove an existing bind so later calls fall back to the next precedence layer. It also states exclusions (path-bound mounts, OAuth token default) which helps avoid misuse. However, it does not explicitly contrast with org_bind or org_context_get, but the purpose is implied strongly.

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