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

With annotations already covering read-only, idempotent, non-destructive, and open-world behavior, the description adds important context: login is required, conversation types differ, only DMs are for exchanging contact info, and 小秘书 is a manual cloud relay. These are behavioral traits beyond what the annotations provide.

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 login requirement, then packs routing and behavioral context into a dense set of clauses. It is concise, though the heavy use of terse Chinese abbreviations makes the structure somewhat cryptic.

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 zero-parameter, read-only list tool with rich annotations and no output schema, the description covers the key selection and usage context: authentication, conversation types, DM-specific behavior, and follow-up tool routing. It does not explain pagination or return shape, but it is sufficiently complete for an agent to select and invoke the tool.

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?

There are zero input parameters, so the baseline is 4. The description does not need to document parameter semantics, and the mentions of activityId/icebreakIntro appear to refer to conversation categories rather than input arguments.

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 states a specific verb and resource: reading one's own conversations, including unread/preview states. It also differentiates conversation types (activityId activity groups, icebreakIntro icebreakers, DM contact exchange) and distinguishes related actions such as invitations and messaging.

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 routes the agent to alternatives for related tasks: pending invitations go to list_my_invitations/respond_activity_invitation, conversation IDs feed into read_messages/send_message, and member/mute actions are handled by get_conversation_members and set_conversation_muted. It does not state explicit when-not-to-use conditions, but the alternatives are clearly named.

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