修改群组

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

With no annotations, the description must carry the behavioral disclosure burden. It clearly states this is a modify operation and documents the unified response format, including code/msg/data and a sample success value. However, it does not mention side effects, permission requirements, or what happens if the topic does not exist.

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 compact and front-loaded: it opens with the endpoint and action, then lists required and optional parameters, then gives the response contract. Every sentence contributes useful information with no filler.

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?

The description covers the request shape, required versus optional fields, and the unified response format, which is important because there is no output schema. It could be more complete with usage conditions or failure behavior, but for a straightforward edit operation it covers the essential calling context adequately.

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 schema already documents each parameter with Chinese labels like 群组编号 and 群组名称. The description merely restates the required/optional grouping without adding meaning beyond the schema, so the baseline of 3 applies.

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 action and resource: '修改群组信息' (modify group information), backed by the endpoint POST /open/topic/editTopic. This clearly distinguishes it from sibling tools like open_topic_add, open_topic_delete, and open_topic_detail.

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?

The description implies this tool is for modifying existing group information, but it never explicitly states when to use it versus alternatives such as open_topic_add or open_topic_delete. No when-not-to-use conditions or alternative tool names are provided.

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