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

Annotations declare readOnlyHint=false, destructiveHint=false and idempotentHint=false, so the write semantics are already structured. The description adds a genuinely new behavioral trait: dynamic membership is applied asynchronously ("users matching the rules are added in the background"). It does not cover permissions, whether duplicate group names are rejected, or what happens if the rules match nobody.

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?

Three sentences, no padding, and the static-vs-dynamic decision is front-loaded before the prerequisite detail. Every sentence carries a distinct instruction.

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 need not be described. For a 3-parameter create tool with annotations covering the safety profile and a fully documented schema, the description supplies the one missing piece an agent cannot get from structured fields: the conditional mode selection and the prerequisite field-lookup step.

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 the schema already documents name, event_id, rule_sets and the nested rule fields. The description's parameter guidance (omit rule_sets for static, only use field_name values from list_rule_fields) largely restates the schema's own field descriptions, adding only the background-matching behavior, so the 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 ("Create a static or dynamic group") and immediately distinguishes the two creation modes an agent must choose between. The read_groups reference signals how this tool relates to the group-management siblings (read_groups, delete_group, add_attendees_to_groups).

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 explicit branch conditions: pass rule_sets for a dynamic group, omit it for a static one. It also names the required prerequisite step (read_groups with action 'list_rule_fields' first) and the constraint on the values it returns, leaving nothing to inference.

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