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

Annotations already declare readOnlyHint=false, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the write/idempotent profile is covered structurally. The description adds nothing beyond that — no statement about whether existing members are preserved, how duplicates are handled, or the 1000-member cap.

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 single sentence is front-loaded and contains no filler, so it is not verbose. However, it is under-specified rather than concise — for a mutation tool with an output schema and a nested Members array, one four-word phrase leaves no room for useful structure.

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?

An output schema exists, so return values needn't be explained, but a mutation tool that accepts up to 1000 member objects and requires an existing group should say so. Nothing is said about partial failure behavior, duplicate handling, or whether the group must pre-exist, leaving real gaps for an agent to guess at.

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%, with both GroupName and Members documented inline including email format, optional display name, min/max items, and a pointer to list_groups. Baseline 3 applies since the schema does the heavy lifting and the description adds no parameter meaning of its own.

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 restates the tool name and title almost verbatim: "Add members to a group" for add_group_members. It conveys the verb and resource but offers no scope or detail that would let an agent distinguish it from create_group, remove_group_members, or create_recipients beyond the name itself.

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?

There is no guidance on when to use this versus siblings such as create_group (which presumably also takes members) or remove_group_members. The description gives no prerequisites (e.g., group must already exist) and no exclusions.

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