MeiGen AI Design MCP

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

The annotation readOnlyHint: false confirms the tool performs writes, which aligns with the 'update' verb. The description adds valuable workflow context about initialization at conversation start, but fails to disclose mutation semantics (persistence guarantees, atomicity) or return value structure given the lack of output schema.

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?

Two sentences with zero waste: the first establishes capabilities and scope, the second provides actionable timing guidance. Information is front-loaded and every clause 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?

Adequate for basic invocation but incomplete given the tool's complexity (8 parameters, 4 action modes) and absence of output schema. The description omits what data structure returns from the 'get' action or success indicators for mutations, leaving a significant gap for an agent expecting to consume preference data.

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 schema already fully documents all 8 parameters including enum values and conditional logic (e.g., 'set' vs 'add_favorite' contexts). The description lists the preference categories but adds no semantic depth beyond what the schema provides, meeting the baseline for high-coverage schemas.

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 dual purpose ('Read or update') and enumerates specific preference resources (style, aspect ratio, model, style notes, favorite prompts). It effectively distinguishes this tool from sibling generation/workflow tools by focusing on user configuration management.

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 specific temporal guidance ('Call with action "get" at conversation start') which establishes a clear usage pattern. However, it lacks explicit 'when-not-to-use' guidance or alternatives for preference management (e.g., when to use 'set' vs 'add_favorite').

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