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

The description adds useful behavioral context beyond the annotations: members can be resolved from any combination of sources, and the group can be addressed by id, slug, or JID. However, it does not explain combination semantics (e.g., union before filters/exclusions), duplicate handling, or side effects. Annotations are minimal and provide no safety or idempotency insight.

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?

Two sentences with no filler. The core action ('Add members to an existing group') is front-loaded, followed by the source-resolution behavior and addressing options. Every clause earns its place.

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?

With 8 parameters, no output schema, and minimal annotations, the description gives a solid overview but leaves operational details to the schema and does not explain how sources combine or what happens when no source is provided. It is adequate but not fully self-contained for a tool of this complexity.

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 all parameters already have descriptions in the input schema. The description reiterates the general concept of combining sources but does not add parameter-level detail beyond what the schema provides. Baseline 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?

States a specific action ('Add') and resource ('members to an existing group') and lists the source types. It is clearly distinct from remove_group_members by verb, but it does not explicitly differentiate from update_group_members, which could also change membership. The name and title reinforce the same purpose.

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 on when to use this tool vs alternatives like update_group_members or remove_group_members, and no mention of prerequisites such as group creation. The only implied usage context is the verb 'Add'.

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