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

Annotations already cover readOnly/idempotent/non-destructive, so the bar is lower. The description still adds value: it explains the risk of guessing (data landing in the wrong organization) and partially discloses the return shape ('kind: api_key' with scopes). It does not detail full response fields, but adds real context beyond annotations.

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?

Front-loaded with the core action, followed by the trigger and the return hint. 'Guessing is how data lands in the wrong organization' is slightly rhetorical but earns its place as a motivating risk statement. Reasonably tight overall.

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?

No output schema exists, yet the description covers the return hint (org API key -> kind: api_key with scopes), the invocation condition, and the consequence of misuse. For a zero-parameter, read-only context resolver this is complete enough to call 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 tool takes zero parameters, so the baseline is 4. There is nothing for the description to clarify about inputs, and it correctly does not invent any.

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?

It states a specific verb and resource: 'Resolve the active organization identity.' Clear what the tool does. However, it does not distinguish itself from nearby siblings like commsharbor_me, commsharbor_organization_get, or commsharbor_platform_context, so an agent has to infer which identity/context tool to pick.

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?

'Read this before a write when you are not certain which tenant is active' gives an explicit invocation condition, and the wrong-tenant warning reinforces the trigger. It stops short of naming alternatives or stating when NOT to call it.

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