assign_realm_role_to_user

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

No annotations provided; description only says 'Assign' and returns a status message. Does not disclose side effects (e.g., idempotency, permission requirements, what happens if role already exists). For a mutation tool, this is insufficient.

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?

Short and to the point, with a one-line summary followed by parameter descriptions. No unnecessary text, but could be slightly more structured (e.g., bullet points for args vs returns).

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?

Lacks details about prerequisites, error handling, or what the status message contains. For a mutation tool with 3 parameters and no annotations, more context (e.g., required permissions, behavior on failure) would be expected.

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 has 0% description coverage, but the description adds meaning: 'user_id' (User ID), 'role_names' (list of role names), 'realm' (target realm with default). However, it does not explain constraints or accepted formats beyond the schema type.

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?

Clearly states 'Assign realm roles to a user' with specific verb and resource. However, it does not differentiate from sibling tools like assign_client_role_to_user or remove_realm_role_from_user, which could cause confusion.

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 versus alternatives. Only mentions a default realm behavior, but lacks when-to-use or when-not-to-use context.

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