The caller, workspace, scopes and memberships

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

readOnlyHint and openWorldHint already establish this as a non-mutating external read, so the description's remaining burden is light. It nonetheless adds nothing beyond annotations: no note that it requires a valid bearer token, whether it reflects the token's scopes vs. stored user scopes, or what an error means when the session is expired.

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?

One short sentence with the endpoint in parentheses — nothing wasted and nothing buried. It is efficient, though it is largely a restatement of the title rather than added information.

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?

With no parameters, no output schema, and annotations covering the safety profile, the tool is simple enough that a terse description is not fatal. Still, since no output schema exists, the description is the only place that could say what the response looks like (user id, workspace id, scope array, membership records), and it only gestures at categories.

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 tool takes zero parameters, so there is nothing for the description to disambiguate and the baseline is 4. The schema coverage figure is trivially 100% on an empty object.

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 names what comes back (caller, workspace, scopes, memberships) and anchors it to GET /v1/auth/me, so an agent can infer this is an identity/context lookup. But it is phrased as a noun list lifted from the title rather than a verb+resource statement, and it draws no line against siblings like members_list or workspaces_create.

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?

There is no when-to-use guidance at all: no mention of calling it first to establish workspace/scope context before other calls, and no exclusion pointing to members_list for other users' data. The agent must infer the call's role from the name alone.

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