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

The description states this is a read ('分页读取'), but the annotations declare readOnlyHint=false, i.e. the operation may mutate state. That is a direct conflict rather than an omitted detail, and unlike the safety-disclosure gaps the annotations do cover (destructiveHint=false, openWorldHint=false), it is not something the agent can reconcile on its own.

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?

Three short sentences, scope stated first, filters second, routing last — well front-loaded with no filler. The sentence about recorded feedback not implying a successful recommendation is terser than it could be, but it earns its place as a caveat.

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?

With an output schema present, return values need no explanation, and the description covers scope, filter values and the cross-tool boundary. It stops short of explaining cursor semantics or result ordering, which matters for a paginated list but is a modest 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?

Schema description coverage is 0%, so the description must carry the load. It partially does: the Chinese status labels map onto the six enum values and '分页' hints at the cursor parameter. However, it says nothing about the OPEN'after' cursor's type-prefixed format (GROUP/INVITATION/CONVERSATION:uuid) or what the cursor is relative to, which the bare pattern string cannot convey.

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 and scope (paginated read of one's own group events, invitations, and existing connections) plus the filter axis, so the agent knows exactly what resource family this covers. The closing pointer to publication_sources distinguishes it from the needs/capability siblings, which is exactly the differentiation the sibling list would otherwise leave ambiguous.

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 explicitly routes the agent elsewhere for a neighbouring concern ('需求和能力来源请使用 publication_sources'), and the status list makes the selection conditions concrete. What is missing is any when-not guidance against the other list siblings (conversations_list, groups_list) that also return overlapping item types.

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