groupChat_setInfoAdminsOnly

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

With no annotations, the description carries the full burden of behavioral disclosure. It only says 'Update,' implying a mutation, but does not disclose whether admin privileges are required, what settings are affected, side effects, or return behavior. This is minimal, non-contradictory but insufficient.

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, front-loaded sentence with no filler, and the '[Group Chat]' prefix gives useful scope. It is appropriately concise, though it under-specifies content.

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 annotations and no output schema, the description must explain the tool's effect and behavior. One vague sentence about updating info group settings is far from sufficient—it omits what the setting does, permissions needed, and expected return values.

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%, and the schema already provides clear descriptions for all three parameters (chatId, sessionId, adminsOnly). The description adds no additional parameter-level context, 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 uses a verb ('Update') and identifies a resource ('info group settings'), but the resource is vague and fails to mention that this specifically toggles the admins-only setting for group info. It does not clearly distinguish it from sibling setters like groupChat_setSubject or groupChat_setMessagesAdminsOnly, which also update group settings.

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 usage guidance is provided—no mention of when to use this tool, prerequisites, or alternatives. The description simply states the action without any contextual cues or exclusions.

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