groupChat_setDescription

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

Annotations are absent, so the description must carry the full burden of disclosing behavior. It only states the action 'Update the group description' without mentioning side effects, permissions, whether an empty description clears the description, or the return value. This is essentially a restatement of the tool's name.

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 a single, front-loaded sentence: '[Group Chat] Update the group description'. It is concise, contains no unnecessary words, and effectively communicates the core action.

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?

Despite the tool's simplicity, the description lacks contextual completeness. It does not explain when this operation is appropriate, what requirements exist (e.g., being a group admin), what happens when the description parameter is empty, or what kind of response is expected. Since there is no output schema, the description should cover these gaps but does not.

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%, with each parameter having a name, example, and description. The description text itself adds no additional parameter information, so the baseline score of 3 is appropriate.

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 clearly states the action with a specific verb and resource: 'Update the group description'. The '[Group Chat]' prefix helps identify the scope, and it distinguishes from siblings like groupChat_setSubject and groupChat_setPicture by naming 'description'.

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 is provided on when to use this tool versus alternatives. There is no mention of prerequisites (e.g., admin rights), nor exclusions, nor differentiation from similar sibling tools like channel_setDescription or groupChat_setSubject.

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