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

No annotations are provided, so the description carries the full burden. It discloses that this is a safe read operation ('Read'), explains the shared-account semantics of `user.id`, and explicitly states what the endpoint does not return. This is reasonable transparency for a simple profile-fetch tool, though it does not detail response shape or auth expectations.

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?

Three sentences, with the primary purpose front-loaded and each subsequent sentence adding a distinct clarification. No filler or redundant phrasing.

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 zero-parameter read-only tool with no output schema, the description is nearly complete: it states what the tool returns, clarifies a key field, and routes users away for organizations. A minor gap is that it does not describe the shape of the platform role or full response payload, but this is not critical for invoking the tool 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 has zero parameters, so the baseline is 4. The description correctly adds no parameter details and instead clarifies an output field (`user.id`), which is appropriate given there is nothing to document about parameters.

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 a specific verb and resource: 'Read the current account profile and platform role.' It also distinguishes itself from organizational listing by noting 'Organizations are not listed here' and directing to a different endpoint, so an agent can tell it apart from siblings like commsharbor_organization_get.

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 an explicit when-not-to-use instruction: 'Organizations are not listed here' and gives the alternative: 'open a workspace by its ID with GET /api/organizations/{organization_id}.' This leaves no ambiguity about which tool handles organization lookups.

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