get_client_scope_realm_scope_mappings

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

With no annotations, the description must fully disclose behavioral traits. It only implies a read operation ('Get') but omits details like required permissions, whether the result is a list or a single role, or any side effects. Minimal information beyond the name.

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 that immediately conveys the core action and resource. No redundant words, perfectly front-loaded.

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 lack of an output schema and the complexity of the tool context (many similar siblings), the description is incomplete. It does not explain the return format, whether results are paginated, or how they relate to other scope mapping tools.

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 are described in the input schema with clear names and types, achieving 100% coverage. The description adds no extra meaning beyond what the schema already provides, which is adequate but not helpful.

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 ('Get') and resource ('realm-level roles') and context ('associated with a client scope's scope'). However, it does not distinguish between this and similar sibling tools like 'get_available_client_scope_realm_scope_mappings' or 'get_effective_client_scope_realm_scope_mappings', leaving ambiguity about which kind of association is meant.

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 is provided on when to use this tool over its many siblings. The description does not mention prerequisites, alternatives, or when not to use it, forcing the agent to rely solely on tool name patterns.

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