groupChat_setMessagesAdminsOnly

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

With no annotations, the description carries the full burden of disclosing behavior. It only says 'Update,' implying a mutation, but does not explain what 'admins only' means, whether existing messages are affected, if special permissions are required, or if the change is reversible. This is a significant transparency gap for a settings-changing tool.

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 short sentence, but it is under-specified and fails to convey the tool's actual function. It is not concise in a useful way; the vague wording does not earn its place and could confuse rather than clarify.

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 tool has 3 parameters and no output schema, so the description is the main source of context. It does not explain the effect of adminsOnly, when to use this tool, or how it differs from related settings tools. This is incomplete for a setting that likely has important behavioral implications.

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 input schema provides 100% coverage with clear descriptions for chatId, sessionId, and adminsOnly. The description adds no parameter-specific meaning, but since the schema handles parameter semantics well, the baseline 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 states 'Update the message group settings,' which identifies a verb and resource but is vague about what specific settings are modified. The tool name 'setMessagesAdminsOnly' implies it controls admin-only messaging, but the description does not mention this, leaving purpose ambiguous and not clearly distinguishing it from sibling tools like groupChat_setInfoAdminsOnly.

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 other groupChat settings tools such as groupChat_setSubject, groupChat_setDescription, or groupChat_setInfoAdminsOnly. The description lacks any contextual clues about intended use cases, prerequisites, or exclusions.

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