set_group_name

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, yet it says nothing about required permissions, whether the rename is reversible, rate limits, or what happens on failure. For a mutation tool with zero annotation coverage, this is a significant gap.

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 line, but the two ':param' lines duplicate the input schema without adding value, so the text is not fully earning its place. It is short, but partly redundant rather than dense.

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?

A mutation tool with no annotations and no output schema should at minimum state permission requirements and expected outcome; the description covers neither. An agent cannot tell from this text whether the call will succeed or what it returns.

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 two ':param' lines simply restate the schema descriptions verbatim ('群号', '新群名称'), adding no format, constraint, or length-limit information. Baseline 3 is appropriate since the schema already documents both parameters.

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 ('修改 QQ 群名称' / modify QQ group name) and cites the OneBot 11 action name, so the agent knows exactly what changes. It does not explicitly contrast itself with similar siblings such as set_group_card or set_group_special_title, so it falls short of a 5.

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, no prerequisites (e.g. bot must be owner/admin), and no mention of alternatives among the many sibling set_group_* tools. Usage must be entirely inferred from the name.

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