get_group_member_list

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

No annotations are provided, so the description carries the full burden, yet it only restates the schema's no_cache field. It says nothing about permissions/auth, response size for large groups, whether the result is paginated, or rate limiting — significant gaps for a tool that can return an entire group's roster.

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 first sentence is front-loaded and efficient, but the two ':param' lines merely re-repeat the schema descriptions, adding length without value. Trimming them would lose nothing.

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 simple read tool with no output schema and fully covered parameters, the definition is adequate but thin: it does not hint at the shape of the returned member list, handling of large groups, or cache-vs-fresh semantics beyond the flag name.

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%, with both group_id and no_cache already documented in the schema. The description's ':param' lines duplicate that text verbatim and add no syntax, format, or edge-case 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?

States a specific verb and resource in Chinese — fetch the full member list of a specified QQ group — and cites the underlying OneBot 11 action. It implicitly distinguishes itself from get_group_member_info (single member) via '全部成员', though it never names that sibling explicitly.

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?

No when-to-use guidance, no exclusions, and no mention of the nearest alternatives (get_group_member_info, get_group_list). The agent must infer that this is the bulk-membership read rather than the single-member read from the tool name alone.

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