Clone a role

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

Annotations already declare destructiveHint=true, non-idempotent, and open-world behavior, so the safety profile is covered structurally. The description adds the real operational requirement (manage_roles permission), which is genuine value, but says nothing about what the clone inherits, whether users/assignments are copied, or that a preview/confirm cycle is required.

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 short sentences, front-loaded with the action, with zero filler. The second sentence largely restates the first ('Clone a role' / 'creates a copy of an existing role'), a minor redundancy.

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?

An output schema exists so return values need no explanation, and the schema covers the execution gates. Still, for a destructive mutation with openWorldHint, the description leaves open what the copy inherits and when cloning is preferable to creating, which an agent would need to choose confidently.

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 100% and the schema itself documents dry_run (default true) and the confirm="YES" gate, so the description need not repeat them. It adds no parameter-level meaning beyond the permission note, so baseline 3 applies.

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 gives a specific verb (clone) plus resource (role) and clarifies it creates a copy of an existing role, which naturally separates it from siblings like create_role and update_role. It stops short of explicitly routing against those siblings, but the clone semantics are unambiguous.

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 clone versus create a role from scratch, no prerequisites beyond the permission string, and no note about the dry_run/confirm workflow an agent must follow before executing.

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