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

Annotations already declare destructiveHint=true, idempotentHint=false, and readOnlyHint=false, so the safety profile is covered; restating "write operation" is redundant. However, the note that changing membership may affect access is a genuine behavioral addition beyond the annotations, so it earns partial credit.

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 short sentences, front-loaded with the action and endpoint, with no wasted filler. Efficient, though it is brief to the point of under-specification.

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 9-parameter mutation with a destructive annotation and no output schema, the description is thin. It omits the required confirm flag, the polymorphic users format, and the multi-workspace account_id/auth requirements that an agent would need to call it correctly.

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 67%, below the 80% threshold, so the description should compensate but does not. It only implies user_group_id via the path and says nothing about the name, users (a three-way anyOf shape), or the required confirm flag.

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 ("Updates a user group/team") and even names the endpoint path, so the operation is unambiguous. It doesn't explicitly distinguish itself from siblings like create_user_group or get_user_group, but the verb alone makes the intent clear.

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 alternatives (create_user_group, delete_user_group) or what prerequisites apply. The "changing membership may affect access" line hints at consequences but offers no when/when-not context.

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