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

Beyond the annotations, the description discloses an important side effect: campaigns that already took the chats retain them after removal. It also adds the batch limit of 200, which is operationally relevant for a destructive write tool. It still does not explain permission requirements or partial-failure behavior, but the annotations already flag destructiveness and non-idempotency.

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, front-loaded sentence that covers the operation, its inputs, the batch limit, and the campaign-retention caveat. Every clause adds practical information, and the '[write]' prefix reinforces the mutation up front.

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 mutation with three parameters and no output schema, the description covers the core behavior, the 200-member cap, and the campaign side effect. It leaves out failure behavior, permissions, and the requirement that at least one list identifier be provided, which are meaningful gaps for a remove operation.

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?

With 0% schema description coverage, the description adds meaningful semantics: tg_list_member_ids are sourced from list_tg_list_members and capped at 200, and the saved list is identified by tg_list_id or tg_list_uuid. It does not clarify that at least one of tg_list_id or tg_list_uuid must logically be supplied, nor does it explain ID format or precedence.

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 ('Removes') and resource ('members ... from a saved list'), making it immediately distinguishable from add_tg_list_members and list_tg_list_members. It also names the ID source and list identifier, leaving no ambiguity about what operation is performed.

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 supplies useful context: member IDs come from list_tg_list_members, at most 200 may be removed, and the list is identified by tg_list_id or tg_list_uuid. However, it does not explicitly state when to use this versus add_tg_list_members or other alternatives, nor does it include exclusions or preconditions.

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