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

With only readOnlyHint in the annotations, the description adds useful behavioral context: login requirement, permission requirement, and the caveat that sources may overlap. It does not describe pagination or return-shape details, so it is not fully transparent.

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 the key prerequisites and usage chain. Every sentence adds practical information without 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 single-parameter read-only list tool, it supplies access requirements, source scope, overlap caveat, and next-step chaining. Return format and pagination are not described, but no output schema exists, so the gap is relatively minor.

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 100% and the sole parameter organizationId is documented in the schema as '组织 id'. The description adds no additional meaning about the parameter, so the baseline of 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 description identifies the resource as activities currently eligible for organization-match invitation and scopes the sources (own organization/featured/my signups/my initiated activities). It implies listing rather than explicitly saying 'list', and distinguishes itself from the sibling invite tool through the chain reference.

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?

It states login is required and matchmaking management capability is needed, which gives clear usage prerequisites. It also gives the downstream chain 'activity id → invite_organization_match_pair_to_activity', telling the agent what to do after listing, though it does not name alternative list tools or explicit exclusions.

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