get_client_granted_scope_mappings

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

Without annotations, the description should convey behavioral traits. It only states 'Get', implying a read operation, but fails to disclose permissions, side effects, or error handling. The description is too minimal to inform the agent about potential failures, return behavior, or required access rights.

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 sentence that immediately conveys the action and key constraint. It is concise and front-loaded, with no wasted words.

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?

The tool has 4 parameters, no output schema, and no annotations. The description does not explain what 'granted scope mappings' are, how the optional 'scope' parameter filters results, or what the return format is. This lack of context leaves the agent underinformed for correct invocation.

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%, and the description adds no new information beyond what is already in the schema. The phrase 'by role container' maps to the 'role_container_id' parameter, but the schema already describes it. The optional 'scope' parameter is not elaborated; the description does not explain its impact. 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?

The description clearly states the verb 'Get' and resource 'granted scope mappings' with context 'for a client by role container'. It directly indicates the action and target. However, it does not differentiate from sibling tools like 'get_client_not_granted_scope_mappings' or 'get_client_scope_mappings_all', as the term 'granted' is ambiguous without further explanation.

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 versus alternatives, such as when to use 'get_client_not_granted_scope_mappings' or other scope-related tools. There is no mention of prerequisites or context for using this tool.

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