update_user_role_user

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

Annotations already set readOnlyHint=false and destructiveHint=false. Description only adds 'WRITE · updates data', which aligns but does not disclose additional behavioral traits like the effect on permissions or the idempotent nature already hinted. No contradiction.

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?

Description is concise at three short lines, front-loaded with the emoji and method. Could be slightly optimized but is clear and to the point.

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?

Despite high schema coverage, the description omits important context: no output format, no mention of conditional requirements (role_id changes required fields, noted in schema but not in tool description), and no differentiation from similar update tools. Incomplete for a write operation with complex conditional parameters.

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?

Both parameters (id, body) are fully described in the input schema (100% coverage). The description adds little beyond the schema, repeating the purpose. However, the schema covers parameter details well, so baseline 3 is appropriate.

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?

Description clearly states the verb 'Update' and resource 'user role', with the line 'Updates the role assigned to the user.' It includes the HTTP method and endpoint, distinguishing it from sibling tools like update_user, update_user_group, etc.

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 guidance on when to use this tool vs alternatives (e.g., update_user for other user fields). Does not mention when not to use it or provide exclusion criteria. The sibling list includes many update tools, but the description offers no selection help.

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