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

Annotations already declare this as a read-only, idempotent, non-destructive open-world operation. The description adds meaningful context beyond annotations: login and match-management permission requirements, pagination by sort score, conversationId-scope behavior, and the output-chain to get_organization_match_pair. It stops short of describing return shape or rate limits, so 4 rather than 5.

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 compact and front-loads login and permission requirements before scope and chaining details. Bracket labels aid quick scanning, though the dense Chinese phrasing and the unexplained conversationId reference slightly reduce clarity.

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 3-parameter list tool with low schema coverage and no output schema, the description supplies important context such as auth, permission, pagination, and the tool chain. It remains incomplete on cursor and userId semantics and on what the returned IDs represent, leaving clear gaps for an agent to resolve.

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 only 33%, with organizationId documented but cursor and userId largely undocumented. The description mentions pagination but does not explain the cursor parameter or userId role, and it references conversationId even though that parameter is absent from the schema, adding confusion rather than compensating for the coverage gap.

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 name and title indicate a list operation over organization match pairs, and the description adds scope ('需撮合管理能力', cloud users, pagination, conversationId restriction) plus the list→get_organization_match_pair chain. It distinguishes itself from get_organization_match_pair by being the list counterpart, though it does not explicitly contrast with siblings like list_my_organization_matches or search_organization_match_people.

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 description states prerequisites ('需要登录', '需撮合管理能力') and points to the follow-up tool get_organization_match_pair for details. However, it does not say when to use this list versus alternative match-list or search tools, so usage is only implied rather than fully guided.

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