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

Annotations already declare the mutation profile (readOnlyHint=false, destructiveHint=false, idempotentHint=false), so the description doesn't need to restate safety. It does add value with the "static groups" constraint and the "manageable" permission hint, but it never says what happens on duplicate membership or with an invalid group id — relevant given idempotentHint=false.

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, zero waste, with the purpose front-loaded and the id-sourcing guidance following. Nothing could be cut without losing information.

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, and the description covers purpose, the static-group constraint, and where to source both ids. The remaining gap is duplicate/error behavior on the pair array, which matters for a non-idempotent mutation.

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 50%: event_id is documented in the schema, but the nested user_id and group_id fields are bare. The description partially compensates by pointing to read_attendees and read_groups as the id sources, but nothing explains the pair-batch batching semantics or whether pairs must be homogeneous.

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 ("Add attendees to static groups"), and the word "static" usefully narrows the operation versus dynamic groups or the sibling remove_attendees_from_groups. It does not explicitly name the counterpart tool, so an agent must infer the add/remove pairing from the verb.

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?

Gives concrete prerequisite routing: use read_attendees for attendee ids and read_groups for manageable group ids. That is real when-to-use context, but there are no exclusions such as what to do if a group is dynamic or if an attendee is already in the group.

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