Bulk update roles

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

It discloses the two-phase commit (first returns count and confirm_token, second applies) and the 3000-member cap with reporting. These behavioral details go far beyond the annotations, explaining why the destructive action is 'safe to call directly' and how it handles large member sets.

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, front-loaded with purpose. Each sentence adds unique value: the operation, the safety mechanism, and the cap/limit. No wasted words.

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?

Given the complexity (6 params, nested filter, no output schema), the description covers the core operation, safety flow, and limit. It reports the affected count and token return. It could mention dry_run or error behavior, but the essentials are present.

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?

The description explains confirm_token's role and the member cap, adding meaning beyond the schema. However, it does not elaborate on filter, dry_run, or action semantics. With schema description coverage at 33%, the description partially compensates but leaves gaps.

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 clearly states 'Add or remove a role across every member matching a filter,' identifying the specific verb, resource, and scope. It distinguishes from sibling single-member tools like assign_role and remove_role by emphasizing the bulk operation across filtered members.

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?

The description implies usage for bulk role changes on a filtered member set. It provides guidance on how to call safely via the two-phase token process. However, it does not explicitly name alternatives or state when not to use, though the bulk scope is evident.

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