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

With no annotations provided, the description carries the full burden and does so thoroughly. It discloses that the binding is session-scoped, leaves other sessions unchanged, is fail-closed, does not change the OAuth token default, and cannot override path-bound mounts—all valuable behavioral context beyond the schema.

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 five dense sentences with no wasted words. The core purpose is front-loaded, and every subsequent sentence adds distinct information about scope, failure behavior, or constraints.

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?

Given full schema coverage, an output schema, and a description that covers side effects, scope, failure semantics, and limits, the definition is complete for an agent to invoke the tool correctly. Nothing essential is missing.

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 already documents slug, scope, and workspace. The description adds no parameter-level meaning beyond the phrase 'authorized org slug', so the baseline 3 applies.

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 ('Bind') and resource ('this MCP conversation or workspace to an authorized org slug'), making the tool's purpose unambiguous. It is clearly distinguishable from siblings like org_unbind and org_list based on the binding action and the session-scope detail.

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 gives clear context on when the binding takes effect ('Subsequent memory/work/file/context calls... resolve under that org') and includes an exclusion ('Path-bound /o/{slug}/mcp mounts cannot be overridden'). However, it does not explicitly mention alternatives such as org_unbind or org_list, so it stops short of full alternative routing.

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