generate_image

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

Annotations indicate this is a destructive operation (destructiveHint=true) and not read-only. The description elaborates on behaviors like automatic compression and upload of local files, and handling of reference images. It does not contradict annotations and adds useful context beyond the 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?

The description is concise, well-structured, and front-loaded with the main purpose. Every sentence provides useful information without redundancy. Tips and platform-specific notes are clearly separated and easy to parse.

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 complexity (10 parameters, multiple providers, no output schema), the description covers the tool's behavior thoroughly, including provider-specific nuances and reference image handling. However, it does not describe the return format (e.g., whether the response includes URLs or base64), which would be helpful for an agent.

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?

All parameters have descriptions in the schema (100% coverage), so the description's role is to add extra context. It does so effectively, e.g., explaining that referenceImages can come from gallery URLs, local paths, or previous results, and clarifying the use of size vs. aspectRatio across providers. This adds value beyond the schema definitions.

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 'Generate an image using AI' and specifies the supported platforms (MeiGen, ComfyUI, OpenAI-compatible APIs). It distinguishes this tool from sibling tools like generate_video and enhance_prompt, establishing a clear purpose.

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 actionable guidance, such as obtaining prompts from get_inspiration() or enhance_prompt() and using gallery URLs as referenceImages. It also includes specific instructions for Midjourney V8.1 style codes. However, it does not explicitly state when NOT to use this tool or list alternatives.

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