get_client_role

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It states the tool 'gets' a role, implying a read operation, but does not mention permissions, side effects, or error conditions. The absence of any behavioral notes beyond the basic action limits 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 concise sentence, front-loaded with the verb and object. It is appropriately short for a straightforward lookup tool, but could be slightly more descriptive without becoming 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 and no annotations, the description should provide more context about what is returned (e.g., role details, composite info) or how the role is identified. With many sibling tools, a hint about the naming convention or uniqueness would improve completeness.

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?

All three parameters (realm, client_uuid, role_name) have descriptions in the schema, and the description does not add extra meaning. Since schema coverage is 100%, the baseline is 3; the description neither enhances nor detracts from parameter understanding.

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 the resource ('a client role by name'). It distinguishes the tool from siblings like 'get_client_role_client_composites' or 'get_client_role_realm_composites' by specifying a direct lookup by name. However, it could be more specific about the context (e.g., within a realm).

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 like 'get_client_role_composites' or 'get_client_role_users'. The description lacks prerequisites, such as needing the realm and client UUID, which are already in the schema but not explained contextually.

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