Updating a specific role

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

Annotations already indicate readOnlyHint=false and destructiveHint=true, so the description's mention of 'updating' aligns. It adds the permission requirement but does not clarify whether the update is partial or full replacement, or any side effects beyond the annotation hints.

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 short (two sentences) but has slight redundancy ('Updating a specific role' repeated as 'Updates a role specified by its ID'). It is mostly front-loaded but could be tighter.

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?

With an output schema present, return values need no description. However, the description omits guidance on the confirm and dry_run parameters, which are crucial for execution safety. More context on the destructive nature and required confirmation would improve completeness.

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% and each parameter has a description. The description adds 'Perm: manage_roles' but does not enhance understanding of parameter semantics beyond what the schema provides. No critical gaps.

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 action (updating a specific role) and the resource (by ID), and distinguishes it from sibling tools like create_role, delete_role, and get_role. The mention of 'Perm: manage_roles' adds context about authorization.

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 does not explicitly state when to use this tool versus alternatives like clone_role or update_role_user. It implies usage via 'updating a role by ID' but lacks explicit guidance on context or exclusions.

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