Updates a QQ group's name using its group ID and the desired new name. Supports group administration via the OneBot 11 protocol.
修改 QQ 群名称 (OneBot 11: set_group_name)。 :param group_id: 群号 :param group_name: 新群名称
| Name | Required | Description | Default |
|---|---|---|---|
| group_id | Yes | 群号 | |
| group_name | Yes | 新群名称 |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It says nothing about required privileges, whether the change is reversible, what happens on failure (e.g. insufficient permission or invalid name), or rate limits — significant gaps for a group-mutating action.
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?
Purpose is front-loaded in one short line, which is good, but the trailing ':param' lines simply duplicate the schema descriptions and consume space without adding information.
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 write operation with no annotations and no output schema, the description omits everything behavioral: permission requirements, failure modes, and side effects on group members. The schema covers the inputs, but the description leaves the operation opaque.
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 both params carry identical text ('群号', '新群名称') in the description, so the description adds no meaning beyond what the schema already provides. Baseline 3 applies when the schema does the heavy lifting.
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: '修改 QQ 群名称' (modify QQ group name), plus the underlying OneBot 11 action name for reference. It is distinct from nearby siblings like set_group_card, set_group_admin, or set_group_portrait, though it never explicitly says so.
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 guidance on when to use this tool, what preconditions apply (bot must be owner/admin), or what alternative exists for renaming other entities. The agent gets no context beyond the bare action.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.