set_group_add_request

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

With no annotations, the description carries the full behavioral burden. It is a mutating, effectively irreversible approval action, yet it says nothing about required permissions (admin/owner), what happens on approval, or error behavior. It only clarifies the approve/reason interaction, which is already in the schema.

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 opening sentence is appropriately front-loaded, but the following four lines duplicate the schema's parameter descriptions word-for-word, which is wasted space given 100% schema coverage.

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 mutating tool with no annotations and no output schema, the description leaves out the key operational context: where the flag comes from and what permissions are needed. It is not complete enough for an agent to invoke it correctly in a real flow.

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 documents all four parameters. The description merely restates the same parameter text verbatim, adding no new syntax, format, or sourcing information for 'flag'.

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: approving/handling group join requests or group invite requests, and names the OneBot 11 action. It is clearly distinguishable from the sibling set_friend_add_request by the 'group' resource, though it never explicitly calls out that distinction.

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 guidance on when to use this tool versus alternatives, nor on the prerequisite that a 'flag' must first be obtained from an event report (e.g. get_group_system_msg / get_recent_notices_and_requests). The agent is told what the params are but not the workflow context.

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