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

With readOnlyHint already true, the description adds meaningful auth requirements ('需要登录', '需撮合管理能力') and privacy behavior ('手机号不下发'). It does not cover rate limits or the full response shape, but the added context is valuable.

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 three compact clauses: prerequisite, returned content, and follow-on chain. It is front-loaded and contains no filler.

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 simple read tool, the description plus annotations and fully documented schema are nearly sufficient: it lists the returned content, auth requirement, and a key privacy omission. Exact output details are absent, but no output schema exists to carry them.

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 100% and both parameters have their own descriptions. The tool description adds no parameter-specific semantics beyond what the schema provides, so baseline 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 definition enumerates returned data (both parties' business profiles, reasons, and channels) and names a follow-on tool, but never explicitly states that it retrieves a match-pair detail record. The agent must infer the verb from the tool name/title.

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 prerequisite login and matchmaking management capability are stated, and the '详情→invite_organization_match_pair_to_activity' chain clarifies when this tool is used. No explicit alternatives or exclusions are provided, but the context is strong.

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