superset_bulk_user_role_replace

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

No annotations are provided, so the description carries the full burden. It discloses the order of operations ('Adds new_role_id first, then removes old_role_id') and the safety mechanism (dry-run via confirm flag). This is transparent for a bulk mutation tool, though it omits potential error conditions or permission requirements.

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: a single-sentence purpose, a note about the safe two-step behavior, and a clear Args block. Every sentence adds value, and the most important information is front-loaded.

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 (bulk role replacement with 4 parameters, no annotations, no schema descriptions), the description covers purpose, behavior, and parameter semantics well. It also explains the dry-run feature and admin exclusion. It doesn't mention return values or edge cases, but an output schema exists, and overall the description is sufficiently complete for an agent to use the tool 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?

The input schema has no descriptions (0% coverage), so the description must compensate. It does so effectively by listing each parameter with a clear explanation (e.g., 'confirm: True to apply. False for dry-run'). This is a strong compensation for the missing schema documentation.

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 the tool performs a bulk role replacement: 'Replace one role with another for all users who have it.' This uses a specific verb+resource+scope and distinguishes it from sibling tools like superset_bulk_user_role_add and superset_bulk_user_role_remove.

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 when to use this tool (when replacing a role across all users) and explains the two-step order, but it does not explicitly name alternatives or state when not to use it. It provides clear context without exclusions, so it exceeds a baseline but stops short of full comparative guidance.

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