get_user_roles

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

The description discloses the core behavior (extracting roles and identity) and supported claim types (standard claims, Keycloak realm_access/resource_access). No annotations are provided, so the description carries the full burden, and it does so adequately, though error handling or limitations are not mentioned.

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?

Two concise sentences front-load the purpose with no wasted words, making it quick to read and understand.

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 description covers the tool's core function and distinguishes it from siblings, but without an output schema, it lacks detail on return format or structure, leaving some ambiguity 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?

With only one parameter 'token' and 0% schema coverage, the description adds meaning by explaining the token is a JWT used to extract roles and identity, going beyond the schema's bare 'token' label.

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 tool extracts user roles and identity information from a JWT, specifically mentioning Keycloak support, which distinguishes it from siblings like decode_jwt or validate_jwt.

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 implies usage for extracting roles, especially from Keycloak tokens, but lacks explicit guidance on when to use this tool vs siblings or any prerequisites.

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