get_group_member_info

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

No annotations are present, and the description does not disclose any behavioral traits like read-only, required permissions, rate limits, or data freshness. For a tool retrieving group member info, basic behavioral context is missing.

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 short and front-loaded with the main purpose, but the argument list is minimal and lacks structure. It is concise but not particularly well-organized.

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?

Given no output schema and low parameter documentation, the description is incomplete. It does not describe the returned information structure, any prerequisites (e.g., must be in group), or error conditions.

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 coverage is 0%, so the description must add value. It provides Chinese translations ('群号', '目标 QQ 号') but these simply restate the parameter names without deeper semantic meaning or format constraints (e.g., integer vs string).

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 clearly states '获取指定群成员详细信息' meaning 'get detailed info of a specified group member', which matches the tool name. However, it does not differentiate from sibling tools like get_group_member_list, which lists members but not details.

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 guidelines are provided about when to use this tool versus alternatives such as get_group_member_list or get_friend_list. The description only explains what it does, not context.

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