superset_role_copy_permissions

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

With no annotations, the description carries the full burden. It discloses that existing permissions will be REPLACED, which is the critical destructive trait, and explains the confirm parameter as a dry-run vs apply toggle. It does not mention auth requirements or rate limits, but the main risk is clearly stated.

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 extremely concise: two sentences plus a bulleted arg list. All key information is front-loaded, with no redundant or filler content.

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 tool with 3 parameters and an existing output schema, the description covers the purpose, parameter roles, destructive replacement behavior, and the confirm/dry-run mechanism. It is complete for the complexity level.

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%, but the description explains every parameter meaning: source_role_id, target_role_id, and confirm, including the critical dry-run/apply semantics. This fully compensates for the bare 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 starts with a specific verb and resource: 'Copy all permissions from one role to another' and explicitly notes 'full replacement'. This clearly states what the tool does and distinguishes it from sibling tools like superset_role_permission_add or superset_role_update.

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 communicates the operation's scope and the replacement semantics, making it clear when to use this tool over granular permission tools. However, it does not explicitly name alternative tools or state when not to use it, so it misses the explicit exclusion guidance.

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