get_group_member_list

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

With no annotations, the description carries full behavioral burden. It usefully adds that the tool is read-only ('只读') and that large groups return hundreds to thousands of records at once, which informs output volume. However, it omits behavioral aspects such as pagination, permissions, or how caching interacts with the no_cache parameter (left to the schema), so it only partially discharges the burden.

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?

Two short clauses separated by a semicolon, front-loading the resource and then adding two critical behavioral flags. Every word earns its place with no redundancy.

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 read-only tool with no output schema, the description covers purpose, read-only nature, and output volume, but it does not mention whether the list is paginated, if there is a maximum return size, or any permission requirements. The no_cache parameter (which controls cache behavior) is not explained in the description, leaving a gap that the schema partially fills.

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 the schema already fully documents both parameters (group_id and no_cache) including usage notes and defaults. The description adds no additional parameter semantics beyond implying a group target, so baseline 3 is appropriate.

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 clear verb ('拉' = fetch) and resource ('某个群的成员列表' = a group's member list), which distinguishes it from get_group_list and get_group_member_info by resource scope. However, it does not explicitly name or contrast with sibling tools, so it remains a clear but non-differentiating restatement of the tool name.

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?

There is no explicit guidance on when to use this tool versus alternatives like get_group_member_info (for a single member). The clause '大群一次几百上千条' hints at a size caveat but does not state when to prefer or avoid this tool, leaving the agent without routing instructions.

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