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

With only destructiveHint=false available, the description carries the full burden and delivers: authentication required, a capability prerequisite, the side effect (three-person group creation plus opener message), a participant exclusion (cloud users cannot join), and a cross-organization quota of 10 per day. These are exactly the behaviors an agent needs before invoking a mutation, and none contradict the annotation.

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?

Two bracketed blocks front-load the hard constraints and then the workflow, with no filler sentences. Every clause carries an operational fact: auth, capability, side effect, exclusion, quota, or confirmation rule.

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 five-parameter mutation with no output schema and a mandatory two-step confirmation, the definition covers auth, prerequisites, side effects, quota, and the confirm loop. The remaining gap is what the preview call actually returns (presumably the hash) and what success looks like, which the agent must infer.

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%, so the baseline is 3, and the description earns an increment by explaining the preview/previewHash contract as a workflow: same parameters replayed with preview=false, and any change invalidating confirmation. The pairId format (userId:userId) is left to the schema, which is acceptable given coverage.

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 gives a specific verb and resource in concrete operational terms: it creates a three-person group and sends an opener message for a match pair. That is far more informative than the title alone. It does not, however, contrast itself against near neighbors such as invite_organization_match_pair_to_activity or introduce_organization_proposal, so the agent must infer which of the family applies.

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?

The '【组合链】' clause prescribes an explicit execution sequence: preview, user verifies names and full message text, then re-call with the original parameters plus previewHash and preview=false, with re-confirmation required on any change. It also states preconditions (login, group-creation capability, cloud users excluded) and a rate limit. It stops short of naming a sibling alternative and the condition under which to prefer it.

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