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

With readOnlyHint already supplied, the description adds useful scope: it requires login and returns conversation metadata such as read state, mute status and icebreak info, while excluding message bodies. The stray instruction about stopping future icebreak is confusing but does not explicitly claim a write behavior for this tool.

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 text is compact and front-loads the read scope, but it is written as semicolon-separated fragments, and the icebreak/snooze sentence is not clearly actionable here and makes the structure harder to parse. It is concise but not well structured.

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 one-parameter read-only tool with no output schema, the description covers the return scope, login requirement, sibling routing and basic workflow. The main gap is the ambiguous icebreak note; otherwise an agent has enough to call it correctly.

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 coverage is 100% for the single conversationId parameter, so the schema already defines the only input. The workflow 'list_my_conversations → 详情' indirectly indicates where to obtain the ID, but the description adds no format or constraint details.

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 specifies a read operation on a conversation and lists what it returns (conversation, member products, read position, mute state, group icebreak info), and explicitly separates message bodies to read_messages. It distinguishes this tool from the key sibling, though the telegraphic wording never states the purpose in one clean sentence.

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 gives an explicit workflow: list_my_conversations → details → read_messages/send_message, which tells an agent when to call it. It also names read_messages for message bodies, but the note about setting snooze/icebreak=false is ambiguous because that action is not available on this read-only tool.

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