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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only says 'List invitations' and does not disclose pagination, filtering, sorting, return shape, or whether the operation requires specific permissions. The verb 'List' weakly implies a non-mutating operation, but nothing else 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?

The description is extremely concise and front-loaded with the core operation. There is no filler or redundant text. It is slightly too terse to carry useful contextual details, but as a short definition it is efficient and scannable.

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 one-parameter list tool, the schema covers the only required input. However, with no output schema and no annotations, the description does not clarify what an invitation record contains, whether results are paginated, or whether the list is scoped beyond organization_id. It is minimally adequate but leaves room for agent uncertainty.

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 schema has 100% description coverage and documents organization_id as 'Active organization ID,' so the schema already explains the only parameter. The description adds no additional meaning about how organization_id is used or what values are acceptable, but with full schema coverage the baseline of 3 is appropriate.

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 a specific verb and resource: 'List invitations.' This clearly identifies the operation as a read-only collection listing. It doesn't explicitly distinguish itself from commsharbor_invitation_create or commsharbor_invitation_accept, but the verb choice makes the purpose unambiguous.

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 guidance about when to use this tool versus alternatives, no mention of prerequisites, and no indication of scope such as whether it lists all organization invitations or only pending ones. The description relies entirely on the tool name and context to convey usage.

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