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

With no annotations, the description carries the behavioral burden. It discloses meaningful behavior: the layered precedence order (path > conversation > workspace > OAuth/token default) and that the result is a snapshot equivalent to org_list. It also references authentication context via 'OAuth / tsk_ token default'. It does not explicitly state read-only/no side effects, but the 'get' name and 'snapshot' language strongly imply a safe read operation.

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 compact and front-loaded: the core purpose is stated first, followed by a concise layered breakdown and a useful equivalence to org_list. Every sentence contributes meaningful information without fluff or repetition of the schema.

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 the tool has one optional parameter, an output schema, and a focused purpose, the description covers the essential context: what is returned, how precedence works, and its relationship to org_list. It could be more explicit about when to use it versus org_list, but for a read-only context lookup the provided information is largely sufficient.

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 coverage is 100%, so the baseline is 3. The description adds value by explaining that 'workspace' corresponds to a binding layer composed of account + repo slug, and by placing it in the precedence hierarchy. This goes beyond the schema's generic 'Optional workspace / repo slug' and helps an agent understand when and why to set the parameter.

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 identifies the tool as returning the current org and bind precedence for the MCP session. It names the resource ('current org', 'bind precedence') and references sibling org_list with 'Same snapshot as org_list', which helps situate it. It lacks an explicit verb phrase, relying on the tool name, but the intent is unambiguous.

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 when to use the tool: to inspect the current org context and binding precedence for the session. It also references org_list by saying the snapshot is the same, which hints at a relationship but does not explicitly state when to choose this tool over org_list or other org tools. The usage context is implied rather than stated with clear exclusions or alternatives.

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