Update group settings

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose that this is a mutating operation and that admin privileges are required, and it names the settings that can be changed. However, it does not describe side effects, whether updates are partial or full replacements, or what the response will contain.

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 concise sentence that immediately lists the main operations and closes with the admin requirement. Every phrase contributes meaning, and there is no redundant or vague wording.

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 7-parameter mutation tool with no annotations and no output schema, the description covers the core intent and the admin prerequisite, but it omits important invocation details such as whether unspecified settings are left unchanged, whether at least one setting must be provided, and what happens on success or failure. It is adequate but not fully complete.

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 only 43%, so the description needs to compensate. It does this well by paraphrasing several undocumented parameters: 'post' maps to who_can_message, 'edit info' to who_can_edit_info, 'add members' to who_can_add_members, and 'join' to join_approval_required. It adds semantic value for four parameters beyond the schema.

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 uses specific verbs (rename, change) and identifies the resource as group settings, listing concrete capabilities: description, posting permissions, editing info, adding members, and join approval. It is clear and distinct from the sibling tools in practice, though it does not explicitly point to an alternative.

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 only usage guidance is 'Requires admin,' which is a prerequisite rather than a when-to-use/exclusion statement. It does not explain when to prefer this over siblings like manage_group_participants or link_group_to_community, or what scenarios are outside its scope.

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