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

Annotations already establish readOnly and idempotent behavior, so the bar is lower, and the description still adds value: it identifies `user.id` as the shared-account ID and discloses a scope boundary (organizations are not returned here). It does not cover auth requirements or the full shape of the returned profile.

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 purpose is front-loaded in a tight first sentence, but the second sentence is long and circuitously worded ('live in the shared account, which does not list them inside products yet'), stacking two related scope caveats into one dense clause. It is not padded, but it is harder to parse than it needs to be.

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?

There is no output schema, so the description carries the return-shape burden. It names the profile, the platform role and `user.id`, but does not indicate what else a profile contains (e.g. email, name, role values), leaving the agent without a full picture of the response.

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 no parameter surface to document. Baseline for a parameterless tool is 4, and the schema coverage signal is effectively moot.

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 first sentence states a specific verb and resource: read the current account profile and platform role. That cleanly separates it from CRUD-style siblings like commsharbor_organization_get and campaign/contact tools. It stops short of naming the closest siblings (commsharbor_context, commsharbor_platform_context), so it is clear but not fully differentiated.

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?

It explicitly states a when-not: organizations are not listed here, and routes the agent to the organization-by-ID call. The alternative is given as an API path rather than the sibling tool name, so the routing is clear but requires the agent to map path to tool.

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