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

Beyond the destructiveHint annotation, the description discloses critical behavior: operations are applied in a fixed order, execution stops at the first refusal, and earlier successful changes remain applied. It also covers permission requirements and the special case of removing oneself.

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 front-loaded with the core purpose and then packs in operation order, permissions, failure behavior, and edge cases without filler. Every sentence carries information needed to invoke the tool correctly.

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 destructive, multi-parameter mutation with no output schema, the description provides the necessary operational context: permissions, parameter ordering, stop-on-first-refusal behavior, and chat-type applicability. Nothing essential for correct invocation is missing.

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 baseline is 3, but the description adds interaction semantics by stating the exact application order (add, admins, notAdmins, title, remove) and the partial-failure behavior. It also reiterates the special meaning of one's own username in 'remove'.

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 a specific verb and resource: changing a group's people, then enumerates the exact operations ('add', 'admins', 'notAdmins', 'remove', 'title'). It also distinguishes direct chats from project chats, so an agent can tell what the tool does and does not apply to.

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?

It clearly scopes usage to group membership changes, notes that only administrators may make changes, and rules out direct chats. It does not explicitly name sibling alternatives (such as create_chat or list_chats), but the usage context is otherwise clear.

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