get_group_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. It does disclose the key trait that this is a read-only (只读) operation, and notes the cache-refresh behavior. However it says nothing about return format, pagination, or ordering, and read-only alone is a thin behavioral profile.

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, front-loaded clauses with no filler: the operation is stated first, then the safety trait and the cache toggle. Every word earns its place.

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 zero-required-parameter read tool with no output schema and full schema coverage, the description is nearly sufficient. It leaves only minor gaps around result ordering/pagination that an agent might want.

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 parameter's meaning is fully documented in the schema. The description's 'no_cache=true 强制刷新' largely restates that definition, adding little beyond it, so the baseline of 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+resource: fetch the list of groups the account has joined (拉取已加入的群列表). This is clearly distinguishable from single-group siblings like get_group_info and get_group_member_list, though it never names an alternative 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?

'只读' plus the no_cache hint implies usage context, but there is no explicit when-to-use vs alternatives guidance (e.g., when to prefer this over get_group_info, or when a cache refresh is warranted beyond the parameter's own definition).

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