generate_image

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

Annotations indicate destructiveHint=true and readOnlyHint=false. The description adds behavioral context: it generates images, supports multiple providers, handles local file compression for referenceImages, and auto-detects provider. However, it doesn't mention potential costs or rate limits, which would be useful for a mutation tool.

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 moderately long but well-structured: main purpose, then tips, then special instructions. Every sentence adds value, though some redundancy could be trimmed (e.g., 'For Midjourney V8.1...' section is detailed but necessary). It front-loads the core action.

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, no output schema), the description is quite complete. It covers all major aspects: providers, parameter usage, special cases (Midjourney style code, local file handling). It lacks a description of return values, but that is acceptable given the absence of 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?

Schema coverage is 100%, so baseline is 3. The description adds value beyond the schema: e.g., for referenceImages it explains sources (gallery URLs, previous results, local paths) and automatic compression; for provider it mentions auto-detection; for workflow it notes default behavior. This enhances the agent's understanding.

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 tool's purpose: 'Generate an image using AI' and explicitly lists supported platforms (MeiGen, local ComfyUI, OpenAI-compatible APIs). It distinguishes itself from sibling tools like generate_video by focusing on image generation.

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 explicit tips: get prompts from get_inspiration() or enhance_prompt(), use gallery image URLs as referenceImages, and specific instructions for Midjourney V8.1 style references (--sref). It also clarifies when not to use certain features (e.g., do not pass URLs via --sref). This helps the agent decide when and how to use the tool.

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