Zitadel MCP

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

Annotations already provide readOnlyHint=true, idempotentHint=true, and destructiveHint=false, indicating safe, repeatable read operations. The description adds value by clarifying the scope ('all roles') and giving examples, but it does not disclose additional behavioral traits like pagination, rate limits, or authentication needs beyond what annotations cover.

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, efficient sentence that front-loads the core purpose ('List all roles defined in a Zitadel project') and includes helpful examples without unnecessary elaboration. Every word contributes to clarity, making it appropriately sized and well-structured.

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 tool's low complexity (one optional parameter), rich annotations covering safety and idempotency, and no output schema, the description is largely complete. It could be improved by mentioning the return format or any limitations, but it adequately supports agent understanding for a read-only list operation.

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 description coverage is 100%, with the parameter 'projectId' fully documented in the schema. The description does not add any parameter-specific information beyond what the schema provides, such as format details or default behavior implications, so it meets the baseline for high schema coverage.

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 specific action ('List all roles') and resource ('defined in a Zitadel project'), with concrete examples ('admin', 'app:finance') that help distinguish it from sibling tools like 'zitadel_list_projects' or 'zitadel_list_users'. It precisely communicates what the tool does without ambiguity.

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 by specifying the resource context ('in a Zitadel project'), but it does not explicitly state when to use this tool versus alternatives like 'zitadel_get_project' or 'zitadel_list_user_grants'. There is no guidance on prerequisites, exclusions, or specific scenarios for selection.

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