Cloning a role

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

The description says 'Creates a copy' implying non-destructive behavior, but the annotation destructiveHint: true suggests the tool destroys something. This is a contradiction. The description adds no further behavioral context beyond the truncated statement and permission requirement.

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 short but ends abruptly with an ellipsis, making it incomplete. While front-loaded with 'Cloning a role', the second sentence is truncated, impairing readability and usefulness.

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 potentially destructive tool (despite description claiming otherwise), important behavioral details like the required confirmation and dry-run mode are missing from the description. The output schema exists but does not compensate for the lack of cloning-specific context.

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 coverage is 100%, so parameters are already described. The description adds no additional meaning beyond the schema, and the mention of 'Perm: manage_roles' is not a parameter but a prerequisite. 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 clearly states 'Cloning a role. Creates a copy of an existing…' which identifies the verb (clone) and resource (role). It distinguishes from create_role and update_role by the name, but does not explicitly differentiate from siblings. The permission hint adds clarity. However, truncation reduces precision.

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?

No explicit guidance on when to use this tool vs alternatives such as create_role or update_role. The description only mentions required permission but fails to provide context for decision-making.

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