remove_client_scope_realm_scope_mappings

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

Without annotations, the description must disclose behavioral traits. It indicates a mutation (removal) but lacks details on idempotency, error handling, permission requirements, or return behavior. The 'roles' parameter's structure is ambiguous ('List of role representations'), reducing transparency.

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, front-loaded sentence with no extraneous information. Efficient, but may be too brief to be fully helpful. Slightly penalized for missing structure that could improve readability (e.g., bullet points for when to use).

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 the tool's complexity (3 parameters, nested object parameter, no output schema) and the lack of annotations, the description is insufficient. It does not explain the roles object structure, return values (e.g., success/error), or edge cases, leaving significant gaps for an AI 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?

The input schema covers all three parameters with descriptions (100% coverage). The description adds no additional meaning beyond stating the overall purpose. For 'roles', the schema says 'List of role representations' but doesn't define the object structure, and the description doesn't clarify.

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 ('Remove'), the resource ('realm-level roles'), and the target ('a client scope's scope'), which effectively differentiates it from sibling tools like remove_client_realm_scope_mappings. However, the phrasing 'client scope's scope' is slightly redundant, preventing a perfect score.

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 (e.g., remove_client_realm_scope_mappings, add_client_scope_realm_scope_mappings). The context is only implied by the name, leaving the AI agent without clear decision support.

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