Clone role

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

Annotations indicate readOnlyHint=false and destructiveHint=false, and description accurately states it creates a new role by copying. No contradictions. However, it could mention required permissions or side effects, but overall clear.

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?

Single sentence of 10 words, no wasted text. Efficiently communicates the core functionality.

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 simple clone operation with annotations present, the description is adequate. It does not state return values, but given no output schema, this is acceptable. Slightly incomplete but still effective.

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 already describes 2 of 3 parameters with descriptions (role and guild). The description does not add any further meaning beyond what the schema provides. For the undocumented 'new_name' parameter, the description offers no guidance. Baseline 3 is appropriate given moderate schema coverage (67%).

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 uses the verb 'copy' and specifies the resource 'role', along with the attributes copied (permissions, color, settings). It clearly distinguishes from sibling tools like create_role (creates from scratch) and update_role (modifies existing).

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 cloning an existing role into a new one, but does not explicitly state when to use it versus alternatives, nor provides any exclusions or prerequisites.

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