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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive), but the description adds real value: login requirement, specific error behaviors (DM 400, no-access 404), and content semantics ('headline' prioritizes activity supply over personal bio, no contact info exposed). This goes well beyond what the annotations state.

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 bracketed shorthand (【需要登录】【组合链】) front-loads the login requirement and packs in constraints efficiently, but the compressed jargon ('DM400 group_only') reads more like telemetry than agent-facing prose. Concise yet at a cost to readability.

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 single-param read-only tool with no output schema, the description covers auth needs, error cases, content semantics, and the surrounding workflow. The main gap is return-shape detail, which is minor given no output schema exists.

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 the single conversationId param is documented with its source ('from list_my_conversations'). The description adds no additional parameter meaning, 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?

The name and title ('群成员名片墙' / group member card wall) make clear this returns members of a group conversation, and the description reinforces scope with '仅本人GROUP成员' (only your own group members). It identifies the resource and a key restriction, though the verb itself is only implied rather than stated outright.

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 concrete usage constraints — only own GROUP conversations, DMs return 400, inaccessible returns 404 — plus an explicit workflow chain (list_my_conversations → members → get_creator → start_conversation). It does not name a sibling to avoid, but the constraint-based routing is genuinely useful.

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