Zitadel MCP

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

Annotations already indicate this is a non-readOnly, non-destructive, non-idempotent operation. The description adds valuable behavioral context by specifying what gets returned (Client ID and Client Secret for confidential clients) and mentioning key configuration aspects like redirect URIs, which helps the agent understand the tool's behavior beyond the basic annotations.

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 appropriately sized with two sentences. The first sentence states the core purpose and return value, while the second mentions configuration aspects. It's front-loaded with the most important information, though the second sentence could be slightly more specific about what 'response types' and 'grant types' refer to.

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 good annotations and comprehensive schema coverage, the description provides adequate context. It mentions the return values (Client ID/Secret) which is important since there's no output schema. The main gap is lack of explicit guidance on when to use this versus update or get operations, but overall it's reasonably complete for the tool's complexity.

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 100% schema description coverage, the input schema already documents all 7 parameters thoroughly. The description adds minimal parameter semantics by mentioning redirect URIs, response types, and grant types configuration, but doesn't provide additional details beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 OIDC application'), the target resource ('in a Zitadel project'), and the return value ('Returns the Client ID (and Client Secret for confidential clients)'). It distinguishes from sibling tools like 'zitadel_create_project' or 'zitadel_create_user' by specifying OIDC application creation.

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 context by mentioning configuration of redirect URIs, response types, and grant types, but doesn't explicitly state when to use this tool versus alternatives like 'zitadel_update_app' or 'zitadel_get_app'. No prerequisites or exclusions are provided.

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