MeiGen AI Design MCP

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

While annotations declare readOnlyHint=true, the description adds valuable behavioral context: 'Free, no API key needed' discloses cost/auth requirements, and 'detailed, high-quality prompt' sets expectations for output quality. It does not contradict the read-only annotation despite using the word 'Transform'.

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?

Three well-structured sentences with zero waste: purpose statement first, usage context second, operational constraints and workflow tips third. Every sentence earns its place by conveying distinct information (function, trigger conditions, cost/workflow).

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 2-parameter tool with complete schema coverage, the description is adequately complete. It provides ecosystem context (integration with gallery tools) and operational constraints (free, no auth). Could explicitly mention the return format (string), but 'detailed, high-quality prompt' provides sufficient implicit context.

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 baseline is appropriately 3. The description references the 'prompt' parameter implicitly through the example ('a cat in a garden'), but adds no semantic information about the 'style' parameter or parameter interactions beyond what the schema already provides.

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 uses a specific verb ('Transform') and resource ('image generation prompt') to clearly define the tool's function. It distinguishes itself from sibling tools like 'generate_image' by emphasizing it creates prompts rather than final images, and references 'gallery inspiration' (likely 'get_inspiration' or 'search_gallery') as a complementary workflow step.

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 when-to-use guidance ('Use when the user provides a brief description... and needs a detailed, high-quality prompt') and suggests workflow integration ('Combine with gallery inspiration'). However, it lacks explicit when-NOT-to-use guidance or direct comparison to alternatives like using raw prompts with generate_image.

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