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

Annotations only declare the generic flags (readOnlyHint=false, destructiveHint=false, idempotentHint=false). The description goes well beyond them by enumerating concrete side effects: leaves the group on the platform, stops syncing, disables AI auto-reply drafts, and keeps the group in discovery (not deleted). This is exactly the side-effect disclosure a mutation tool needs.

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?

Front-loaded with the core action, then a scannable 'What this does' list and a 'Returns' line. Every bullet is informative, though the first bullet mildly restates the opening sentence ('stop syncing its messages' / 'Stops syncing new messages').

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 non-idempotent mutation tool with no output schema, the description covers the full picture: reversibility, side effects, and the return payload (success, thread_id). Nothing needed to invoke or reason about the call 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 description coverage is 100%, and the schema itself explains both group_id (discovered id or platform chat id) and in_workspace. The description adds no parameter-level detail, so the schema does the heavy lifting and baseline 3 applies.

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?

States a specific verb and resource ('Leave a group') and immediately scopes the effect ('stop syncing its messages to your inbox'). It is clearly distinguishable from siblings like group_join or group_add because it names the resulting state ('moved back to discovered state').

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 gives clear usage context: it explains the state transition from monitored to discovered and that the user 'can rejoin later', which tells an agent when this is the right action. It does not, however, explicitly name alternative siblings (e.g. group_join vs group_add) or state when NOT to call it.

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