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

Beyond the readOnlyHint annotation, the description discloses concrete runtime behavior: login required, DM conversations rejected with 400 group_only, inaccessible conversations return 404, and — importantly — no contact details are returned and no in-group contact exchange happens. That is real added context; it stops short of describing response shape or pagination.

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?

Extremely dense but front-loaded: access precondition first, behavioral constraints second, navigation chain last. Nothing is filler, and the telegraphic style still parses cleanly.

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 tool with no output schema, the definition covers auth, scoping, error semantics, privacy limits, and follow-on tools — sufficient for correct invocation. Only the returned fields' structure is left vague, which is acceptable since 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?

With a single parameter and 100% schema coverage, the schema already documents conversationId and even its source ('从 list_my_conversations 拿'). The description's repeated mention of list_my_conversations adds no new meaning beyond that, 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 description conveys that this returns member/profile-card data for a group conversation ('仅本人GROUP成员', 'headline优先活动供给再个人简介'), but never states a clear verb+resource like 'list the members of a group conversation'. It also doesn't distinguish itself from nearby siblings such as list_chain_group_members or list_organization_members, so an agent must infer the boundary.

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?

The flow 'list_my_conversations→成员→get_creator→start_conversation' explicitly tells the agent where the conversationId comes from and which tools to call next. Preconditions ('需要登录', '仅本人GROUP成员') are stated, though no explicit when-not-to-use rule versus alternates is given.

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