update_group_setting

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

With no annotations, the description carries full burden but only mentions the effect (changing settings). It does not disclose side effects, permissions needed, idempotency, or error conditions. Basic behavior is described, but significant transparency gaps remain.

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, focused sentence with no redundancy. Every word contributes to explaining the tool's action, achieving high conciseness.

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 the tool's mutation nature, the description lacks details on return values, success indicators, or preconditions like admin rights. It covers the basic effect but is incomplete for full autonomous usage.

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?

The description adds meaning to the action parameter by linking 'announcement' to sending messages and 'locked' to editing info, going beyond the enum values in the schema. It does not explain 'not_announcement' or 'unlocked', but these are inferable. Overall, enhances parameter understanding.

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 identifies the tool's purpose: changing group settings related to who can send messages (announcement) or edit info (locked). It uses specific verbs and resources, effectively distinguishing from siblings like update_group_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?

The description implies when to use this tool (to alter announcement or locked settings), but does not explicitly state when not to use it or mention alternatives. No guidance on prerequisites or exclusions.

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