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

Annotations already declare readOnly/idempotent/non-destructive/openWorld, so the bar is lower; the description usefully adds the login requirement and clarifies that message bodies are NOT returned here. However, the line '停未来自动破冰设snooze/icebreak=false' uses '设' (set), which reads like a mutation instruction and sits awkwardly against readOnlyHint — ambiguous enough to be confusing without being a clear contradiction.

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?

Login requirement is front-loaded, which is good, but the body is a densely compressed run-on of slash-separated fragments and bracket tags that is hard to parse. Some clauses (snooze/icebreak, group-leave) feel tangential to a read-only detail fetch and dilute the core message.

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, the description correctly compensates by enumerating the returned fields, the auth prerequisite, and the relationship to message-reading tools. Complete enough for an agent to call it correctly, though the ambiguous set/leave clause is a minor loose end.

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 there is a single required conversationId, so the schema fully documents the parameter. The description adds no format or sourcing detail for conversationId beyond what the schema provides, so the baseline 3 applies.

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 (read own conversation detail) and enumerates the payload fields (mute, read position, icebreak, members/products), and explicitly separates itself from read_messages for body content. Distinguishable from the content-reading sibling, though the field list partly overlaps with get_conversation_members/get_conversation_needs, which muddies the boundary slightly.

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 alternative ('正文另用read_messages') and a workflow chain (list_my_conversations→详情→read_messages/send_message), plus a login prerequisite. It names when to reach for read_messages instead, but the trailing notes about snooze/icebreak and leaving a group are not clearly attributed to this tool vs. neighbors, so the routing is not fully airtight.

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