Get Member Organizations

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

No annotations are provided, so the description must carry behavioral context. It communicates a read-style operation, clarifies the workspace terminology, and explains the 'me' sentinel. Still, it does not disclose authentication needs, response shape, or potential error behavior, which is a meaningful gap for an unannotated tool.

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 short sentences with no filler. The primary purpose is front-loaded, and the 'me' tip is the only additional information, earning 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 simple one-parameter read-only lookup, the description is mostly complete: it identifies the resource, the relationship, and the special 'me' value. There is no output schema, so a brief note on the return shape would be marginally helpful, but the description still gives an agent enough context to invoke it correctly.

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?

The input schema already covers memberId with 100% description coverage, including the 'me' usage. The tool description only paraphrases the schema's use-of-'me' hint and adds no new parameter meaning or constraints.

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 uses a specific verb ('Get') and resource ('organizations (workspaces)') and clearly scopes it to those a member belongs to. This differentiates it from sibling tools like get_organization_members, which list members of an organization, and get_organization, which fetches a single organization.

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 a clear usage context: retrieve all workspaces for a member, including 'me' for the authenticated user. However, it does not explicitly contrast this with alternative sibling tools or state when not to use it, leaving the selection logic mostly implied.

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