evolution_group_update_setting

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

With no annotations provided, the description carries the full burden. It does not disclose permissions required (e.g., admin), side effects, reversibility, or error conditions. The enum values in the schema provide some context, but the description adds no behavioral insights beyond 'update'.

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 sentence with clear front-loading of the verb and resource. It is concise and to the point, though it could include more context without being overly verbose.

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?

Given no output schema and no annotations, the description lacks completeness. It does not explain return values, error handling, or prerequisites. The tool requires admin privileges typically, but this is not mentioned. For a mutation tool, this is insufficient.

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 coverage is 100%, so the schema already documents all parameters. The description adds minimal value by mapping 'who can message / edit info' to the action parameter, but does not clarify the optional 'instance' parameter or provide further semantics 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 clearly states the verb (update), resource (group settings), and scope (who can message / edit info). It effectively distinguishes from sibling tools like evolution_group_update_description and evolution_group_update_subject by focusing on messaging and editing permissions.

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 usage for changing messaging and editing permissions, but does not explicitly state when to use this tool vs alternatives like evolution_group_update_participant or evolution_group_toggle_ephemeral. No exclusions or prerequisites are mentioned.

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