Zitadel MCP

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

Annotations indicate this is a non-read-only, non-idempotent, non-destructive operation, which the description aligns with by implying creation (a write). It adds minimal behavioral context beyond annotations—mentioning that projects contain applications, roles, and grants—but doesn't cover aspects like permissions needed, rate limits, or error handling.

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 concise (two sentences) and front-loaded with the core purpose. The second sentence provides useful context without redundancy. It could be slightly improved by integrating usage hints, but it's efficient overall.

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?

For a creation tool with no output schema and moderate complexity (3 parameters), the description is minimally adequate. It covers the purpose but lacks details on usage, behavioral traits beyond annotations, and output expectations. With annotations providing safety info, it's not incomplete, but gaps remain.

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%, so parameters are well-documented in the schema. The description doesn't add any semantic details about parameters beyond what's in the schema (e.g., explaining 'projectRoleAssertion' further), but it doesn't need to given the high coverage. Baseline 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 action ('Create a new project') and resource ('in Zitadel'), with additional context about what projects contain. It distinguishes from siblings like 'zitadel_create_user' or 'zitadel_create_oidc_app' by focusing on projects, though it doesn't explicitly contrast with 'zitadel_get_project' or 'zitadel_list_projects'.

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. It doesn't mention prerequisites (e.g., needing admin permissions), compare to sibling tools (e.g., 'zitadel_get_project' for reading), or specify scenarios for project creation (e.g., initial setup vs. adding new projects).

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