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

Annotations indicate non-readonly, idempotent, open-world, non-destructive behavior. The description adds important context beyond that: login required, a new group is created and a message is sent as the user, server-side validation of introduce capability/participants/blocklist/daily frequency, a cap of 10 cross-organization introductions per manager per day, and existing groups returning conversationId without resending the opener.

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-loads the most critical constraints: login requirement, group creation, message sending, and preview workflow. Dense but free of filler; every sentence adds operational meaning. Slightly harder to parse due to high information density, but appropriate for the tool's complexity.

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 complex mutation with no output schema and annotations that only cover safety hints, the description supplies the preview workflow, authentication need, side effects, validation rules, rate limits, and return behavior. Nothing needed for correct invocation is missing.

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 coverage is 80% and already documents preview, proposalId, previewHash, and organizationId. The description adds meaning beyond the schema: message must be the agent-written opener text shown to the user, previewHash must be from the latest preview, and an org-match pairId cannot replace proposalId. OrganizationId semantics remain schema-only.

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?

States a specific action: only for PAIR proposals, creates a group and sends an opener as the user after confirmation. Explicitly distinguishes proposalId from org-match pairId, helping separate it from the introduce_organization_match_pair sibling. Clear verb, resource, and scope.

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?

Prescribes the two-step flow: preview=true to show both parties and the message, then the same parameters plus previewHash with preview=false to execute. States it is only for PAIR proposals and explicitly forbids substituting an org-match pairId. No ambiguity about when and how to use it.

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