delete_user_client_role_mappings

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action (delete) without explaining consequences (e.g., irreversible removal, effects on user permissions, error handling if no mappings exist). This is insufficient for an agent to understand side effects.

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 a single, concise sentence (12 words) that efficiently conveys the core purpose. While not structured with sections, it is front-loaded and contains no fluff. It could benefit from additional context but remains non-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?

Given no output schema, no annotations, and a complex 'roles' object parameter, the description is incomplete. It does not explain return values, prerequisites (e.g., user existence, client existence), or the structure of the roles object. The minimal description leaves significant gaps for an agent.

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 documented. However, the description adds no extra meaning beyond the schema. The 'roles' parameter is an object without further format or example, but the schema already provides a basic description. 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?

The description clearly states the verb 'Delete' and the resource 'client-level role mappings' with the target 'from the user', which precisely distinguishes it from sibling tools like delete_group_client_role_mappings (which targets groups) and add_user_client_role_mappings (which adds).

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 provides no guidance on when to use this tool versus alternatives (e.g., delete_group_client_role_mappings or add_user_client_role_mappings). It does not mention any prerequisites, cautionary notes, or use cases, leaving the agent to infer context.

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