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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context beyond this: login is required, only the current user's own conversations are accessible, and non-empty icebreakIntro indicates an icebreak introduction group. No contradiction with annotations; no rate limits or error behavior mentioned, but the safety profile is already covered.

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 front-loaded with purpose and scope, then uses structured sections to explain the non-obvious icebreakIntro field and related tools. Every sentence adds operational value, and the line breaks make it easy to scan. It is detailed without being padded.

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?

There is no output schema, so the description correctly takes on the burden of explaining what is returned, listing the key fields and decoding icebreakIntro semantics. It also covers authentication, access scope, and alternatives. For a single-parameter read-only tool, this is complete enough for an agent to select and invoke 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% and the schema describes conversationId as '会话 id'. The description adds the important eligibility semantic that the ID must refer to a conversation the current user participates in, reinforcing '只能查自己参与的会话'. This goes slightly beyond the schema's bare parameter description.

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: '返回当前用户参与的某个会话的详情', and enumerates the exact returned fields (成员 / 关联产品 / 最近预览 / 我的已读位 / muted / icebreakIntro). It also differentiates from close siblings by explicitly pointing to read_messages for reading messages and get_conversation_members for member cards.

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?

Provides explicit routing: '读消息用 read_messages' and '群成员名片墙用 get_conversation_members'. It also explains when to use set_notification_prefs with icebreak:false, icebreakSnoozeUntil, and leave_conversation for icebreak-related preferences. The constraint '只能查自己参与的会话' clearly states when the tool should not be used.

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