MeiGen AI Design MCP

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

The annotations declare destructiveHint: true, implying the tool destroys or deletes data, but the description frames the tool as purely creative ('Generate an image'). The description fails to explain any destructive behavior (such as overwriting existing files) or reconcile this contradiction, despite providing other behavioral details like automatic file compression.

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?

Four sentences with zero waste: sentence 1 states purpose and scope, sentence 2 provides workflow tips linking to siblings, sentence 3 states a critical model restriction, and sentence 4 gives specific instruction for prompt enhancement. Information is front-loaded and every sentence earns its place.

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 high complexity (9 parameters, 3 providers with different behaviors), the description comprehensively covers provider-specific behaviors, file handling for references, and model constraints. It lacks only a description of the return value (image data/URL), which would be helpful given the absence of an output schema.

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 coverage, the baseline is 3. The description adds valuable workflow context beyond the schema: it links the prompt parameter to get_inspiration/enhance_prompt, clarifies referenceImages accepts gallery URLs, and provides model-specific constraints (Niji 7 limitations) that inform the model parameter selection.

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 opens with a specific verb-noun pair ('Generate an image') and immediately clarifies the supported platforms (MeiGen, ComfyUI, OpenAI-compatible), distinguishing it from sibling tools like comfyui_workflow which manages workflows rather than generating images.

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?

Provides explicit workflow guidance: recommends using get_inspiration() or enhance_prompt() for prompts, specifies using gallery URLs for referenceImages, and includes a clear when-not-to-use constraint ('Midjourney Niji 7 is for anime/illustration ONLY'). Also specifies the correct style parameter for enhance_prompt when using Niji 7.

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