add_user_realm_role_mappings

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

Description is minimal ('Add...') with no annotations. It does not disclose whether the operation appends or replaces, required permissions, or side effects. 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?

Description is very concise (one sentence) but may be too terse given the complexity of the tool and its siblings. Could include more context without being verbose.

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?

No output schema and no annotations; description fails to explain the roles parameter format (e.g., expected structure), whether operation is additive, or return value. Incomplete for effective use.

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?

Input schema covers all parameters with descriptions (100% coverage). The description adds no additional meaning beyond the schema, so baseline score of 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 it adds 'realm-level role mappings to a user', specifying the action (add) and resource (realm-level role mappings to a user). This distinguishes it from siblings like add_group_realm_role_mappings (group-level) or add_user_client_role_mappings (client-level).

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 versus alternatives. Given many sibling tools for role mappings (e.g., add_group_realm_role_mappings, add_user_client_role_mappings), the description fails to explain the context or prerequisites.

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