set_group_add_request

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

No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that 'reason' only takes effect when approve=False, but for an admin mutation it says nothing about the required group-admin/owner privileges, whether the action is reversible, or what the result is. Significant gaps remain.

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 purpose is front-loaded in the first sentence, but the ':param' block duplicates the schema almost word-for-word, adding length without new information. Structure is adequate but includes redundant content.

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 permission-gated mutation tool with no annotations and no output schema, the description should convey auth requirements and outcome. It does not, leaving key operational context missing even though parameter definitions are fully covered by the schema.

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 baseline is 3. The description's per-parameter text is essentially verbatim from the schema (flag, sub_type, approve, reason), adding no meaning beyond what the schema already documents.

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 specific verb and resource ('审批处理加群请求或邀请入群请求' - approve a group join request or invitation) and cites the OneBot 11 action name. This clearly distinguishes it from set_friend_add_request, a sibling handling friend requests, though it doesn't call that sibling out 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?

It explains what sub_type 'add' vs 'invite' mean, which helps the agent choose the right call shape, but there is no guidance on when to use this tool versus alternatives, where the required 'flag' comes from, or any permission prerequisites. Usage context is left to inference.

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