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

Annotations already declare read-only/idempotent/non-destructive, but the description adds genuinely new context: login is required, results are filtered by audience/block/hide settings, INVITED entries are included with their true participation status, and the listing is explicitly not an attendance commitment. That privacy-filtering and status-semantics detail goes beyond the annotation set.

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?

Compact and front-loaded: the login prerequisite and the filtering behavior come first, and the follow-up routing sits at the end. Every clause carries information; a slightly tighter split between the query semantics and the next-step guidance would be ideal.

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 single-param read tool with no output schema, the description covers access requirements, filtering rules, and the meaning of returned statuses (INVITED, real participation, no attendance guarantee), which is what an agent needs to interpret results. It is silent on ordering, volume, or pagination, which is a minor residual gap.

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?

Only one parameter exists and schema description coverage is 100% (活动 id 或 slug), so the schema already carries the full parameter meaning. The description adds no format detail about activityRef, making the baseline 3 correct.

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 verb+resource (查本人匹配 for this activity) and adds the scoping rule: results follow the user's current audience/block/hide settings. It is concrete enough to understand the operation without opening the schema, but it never names or distinguishes itself from near siblings such as get_my_activity_match_group or list_my_match_preferences.

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?

Gives a clear prerequisite (需要登录) and routes the agent to the correct follow-up step: after the user consents, call create_connection_request, with cloud users on the manual relay path. It stops short of stating when this tool should be chosen over the other match/preference listers, so it is clear context without exclusions.

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