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

Annotations only declare readOnlyHint=true, so the description carries the domain burden and does add real value: it discloses that the result surface includes unread/preview state, that contact exchange happens only in DMs, and that the 小秘书 channel is a manual cloud relay rather than an automated bot. It does not cover pagination, ordering, or size limits of the listing.

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?

Every fragment carries information, but the semicolon-chained, mixed-language shorthand makes it hard for an agent to scan, and the routing pointers are buried mid-string rather than front-loaded. It is dense rather than wasteful, but the structure is poor.

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 no output schema and no parameters, the description is the only source of truth about what comes back; it names the conversation types and unread/preview state but never describes the response shape, ordering, or how icebreak/secretary entries appear. Adequate for invocation, incomplete for interpreting results.

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?

The tool takes zero parameters, so the baseline of 4 applies; there is nothing the description must disambiguate. The mention of activityId and icebreakIntro refers to conversation-type fields in the data rather than inputs, so it adds context without creating parameter ambiguity.

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 opening clause "读本人会话、未读/预览" states a specific verb+resource (read my own conversations, including unread/preview) and immediately distinguishes conversation kinds (activity group vs. icebreak DM). It does not distinguish itself from the sibling get_conversation, and the telegraphic style forces the reader to parse before the purpose lands, so it stops short of a 5.

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 to alternatives explicitly: pending invitations go to list_my_invitations/respond_activity_invitation, ids feed read_messages/send_message, member reads go to get_conversation_members and muting to set_conversation_muted. What is missing is an explicit 'use this when/when not' framing, and the routing is written as fragments rather than conditional guidance.

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