List authorization resources

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

Description adds behavioral details beyond annotations: stating read-only, idempotent, return format (JSON array or error text), consistent with annotations and no contradictions.

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?

Description is concise, well-structured, front-loads core action, followed by behavior, usage instructions, and return info. No extraneous 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?

Given no output schema, the description fully explains return format and error case. It also provides context on prerequisites and sibling tool relationships, making it complete for the tool's simplicity.

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?

Input schema already provides a thorough description for clientId (internal UUID, how to obtain). The description reinforces this but does not add new semantic meaning beyond schema coverage, keeping baseline at 3.

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 lists authorization resources on a Keycloak client and distinguishes it from sibling tools for policies and permissions by specifying 'protected resources that policies and permissions apply to'.

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?

Explicitly advises to call keycloak_clients_list first for the client internal id, and to pair with keycloak_authz_policies_list and keycloak_authz_permissions_list for a full picture, providing clear when-to-use and combinatorial guidance.

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