superset_bulk_user_role_add

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the non-removal of existing roles, the selection logic, the exclude_admin default, and the dry-run behavior. It does not disclose edge cases like idempotency (what happens if a user already has the role), but the core behavior is transparent enough for an agent to safely invoke the tool.

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?

The description is concise and well-structured. It opens with a clear one-sentence purpose, then uses an Args list to describe parameters without redundancy. Every sentence contributes value, and the format is easy to scan.

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 tool's complexity (5 parameters, two selection modes, dry-run option), the description covers all essential guidance. The presence of an output schema means return-value details are not needed in the description. An agent has enough information to select and invoke this tool correctly, including how to avoid unintended modifications via the confirm flag.

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 description coverage is 0%, so the description must fully compensate. It does so by explaining every parameter (role_id, user_ids, filter_role_id, exclude_admin, confirm) and their interdependencies, including the relationship between user_ids and filter_role_id. This adds substantial meaning beyond the bare input schema.

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 states a clear, specific verb and resource: "Add a role to multiple users." It also distinguishes from sibling tools by noting "without removing existing roles," which sets it apart from superset_bulk_user_role_remove and superset_bulk_user_role_replace. The purpose is unambiguous and specific.

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 gives clear usage context: it explains the two selection modes (explicit user IDs vs. current role filter), notes that filter_role_id is ignored when user_ids is set, and mentions the dry-run capability via confirm. It implies when to use this tool (additive role changes) but does not explicitly contrast with alternative tools. Still, the guidance is practical and actionable.

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