im_get_chat_members

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It merely states the action without revealing pagination behavior, permissions, or whether the operation is read-only. The lack of detail means the agent cannot anticipate limitations or side effects, which is a significant gap for a tool with pagination parameters.

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 a single short phrase with no filler or redundancy. It is extremely concise and front-loaded with the core purpose. However, its brevity borders on under-specification, but for the purpose it fulfills, there is zero wasted text.

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 and no annotations, so the description should compensate by explaining response structure, pagination limits, or error conditions. It does not. The tool has 3 parameters and a pagination mechanism that is entirely unexplained. While the core purpose is clear, the lack of behavioral and return-value context leaves the description incomplete for reliable invocation.

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%, so all three parameters (chat_id, page_size, page_token) have individual descriptions. The tool description adds no extra meaning beyond the schema, but since the schema is complete, the baseline of 3 applies. No additional parameter nuances are disclosed.

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 '获取群成员列表' (get group member list) clearly states the action (get) and resource (group member list). It is distinct from sibling tools like im_list_chats or im_send_message, though it does not explicitly differentiate itself. The verb and object are clear, making the purpose unambiguous.

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 description provides no guidance on when to use this tool versus alternatives. It does not mention prerequisites, typical contexts, or why one would choose this over other IM tools. There are no exclusions or alternative references, leaving the agent without directional help.

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