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

With no annotations, the description carries the behavioral disclosure burden. It does disclose an important behavior — the acceptance token is revealed exactly once — which is non-obvious and operationally critical. It does not, however, mention side effects such as whether an invitation email is sent, permission requirements, or what happens after the token is revealed.

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?

A single tight sentence that front-loads the action and includes the critical one-time-token caveat. No filler words or redundant restatement of the tool name.

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?

The tool is simple and well-parameterized, and the description covers the core behavior and the one-time token constraint. However, there is no output schema, and the description does not specify the response shape or how the returned token relates to commsharbor_invitation_accept, leaving some ambiguity for correct invocation.

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?

Schema description coverage is 100%, so the parameters are already documented. The description adds no additional parameter-level detail, such as allowed role values or the exact format of the email and organization ID, so it stays at the baseline.

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 states the exact action ('Invite a member') and the distinctive result ('reveal the acceptance token once'). This makes it immediately distinguishable from sibling tools like commsharbor_invitation_accept and commsharbor_invitations while still naming the resource.

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?

Usage is implied: when the goal is to invite a member, this is the tool. However, there is no explicit guidance about when to prefer it over related siblings such as commsharbor_invitation_accept, nor any exclusion criteria or prerequisites.

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