Zitadel MCP

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

Annotations already indicate this is a read-only, idempotent, non-destructive operation. The description adds valuable context beyond this by specifying the output format ('ready-to-paste configuration' for .env.local) and the purpose (fetching app details for environment variables), which helps the agent understand the tool's specific behavior and use case.

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 two concise sentences that are front-loaded with the main purpose. Every word earns its place by clearly explaining what the tool does and its specific output format, with no wasted text or redundancy.

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 moderate complexity (2 required parameters, no output schema), the description is mostly complete. It explains the purpose, output format, and context well, but doesn't detail potential errors, authentication requirements, or rate limits, which could be helpful for an agent despite the annotations covering safety aspects.

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 clear descriptions for both parameters ('projectId' and 'appId'). The description doesn't add any additional semantic information about these parameters beyond what the schema provides, so it meets the baseline of 3 for adequate coverage without extra value.

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 ('Get the environment variables'), the resource ('app details'), and the output format ('formats them as ready-to-paste configuration'). It distinguishes itself from sibling tools like 'zitadel_get_app' by specifying the unique formatting purpose for .env.local files.

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 when to use this tool ('for a new application's .env.local file'), but it doesn't explicitly mention when not to use it or name alternatives. For example, it doesn't contrast with 'zitadel_get_app' which might return raw app details without formatting.

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