Zitadel MCP

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

Annotations already indicate destructiveHint=true and idempotentHint=true, but the description adds valuable context by specifying that 'confirm: true' is required to execute and that omitting it allows previewing the action. This clarifies the tool's safety mechanism and preview behavior, enhancing transparency beyond the annotations without contradicting them.

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 extremely concise with two sentences that are front-loaded and waste-free. The first sentence states the purpose, and the second provides critical usage guidance, with every word earning its place to aid the AI agent efficiently.

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 complexity as a destructive operation with a confirmation mechanism, the description is reasonably complete. It covers the purpose and a key behavioral trait (confirm requirement). However, without an output schema, it does not describe return values or potential errors, and it could benefit from more context on when to use versus siblings, slightly limiting completeness.

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?

The input schema has 100% description coverage, providing clear details for userId, grantId, and confirm parameters. The description adds minimal semantics by emphasizing the requirement for 'confirm: true', but does not elaborate further on parameter meanings or usage beyond what the schema already documents, aligning with the baseline score 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 ('Remove a role grant from a user') and identifies the resource ('by grant ID'), distinguishing it from sibling tools like 'zitadel_delete_user' or 'zitadel_deactivate_user' which affect the user entity differently. It precisely communicates what the tool does without being vague or tautological.

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 provides clear context for usage with 'Requires confirm: true', indicating a prerequisite for execution. However, it does not explicitly state when to use this tool versus alternatives like 'zitadel_list_user_grants' for viewing grants or other user management tools, nor does it specify exclusions or edge cases.

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