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

Annotations cover safety flags (destructiveHint, idempotentHint), but the description adds meaningful behavior beyond them: the patch semantics of omitted fields, the replacement (not additive) nature of userIds, required role, and the immutable built-in group. These are exactly the traits an agent needs before mutating membership.

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?

Four tight sentences, front-loaded with the action, then partial-update semantics, then the destructive-replacement caveat, then prerequisites and the immutable exception. No sentence is wasted.

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 mutation tool with no output schema, the description covers the critical concerns: side effects (membership replacement), partial-update behavior, auth requirements, and the edge case of the built-in group. Nothing essential to calling it correctly is missing.

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 baseline is 3, but the description adds semantics the schema does not: 'userIds, when sent, is the whole membership' clarifies replace-not-append behavior, and 'what you omit is kept' frames name/groupId as optional patches. This meaningfully extends the schema docs.

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 specific verbs and resource: 'Renames a group or sets its members.' This clearly separates it from siblings like create_access_group, delete_access_group, and list_access_groups. An agent can tell what the tool does without opening the schema.

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 clear operational context: partial-update semantics ('What you omit is kept'), prerequisites ('needs Owner or Admin'), and an exclusion ('Everyone is built in and cannot be renamed or emptied'). It does not explicitly name alternatives (e.g., delete_access_group for removal), so it stops short of full routing guidance.

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