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

No annotations are provided, so the description carries the full burden. It discloses the internal pipeline (Groq enhancement, Pollinations rendering), the return format ('direct image URL + markdown embed'), inline rendering behavior, and quota details ('5 free/day · Zambo Pass: unlimited'). This goes well beyond the schema and gives the agent clear expectations.

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 compact at roughly six sentences and front-loads the purpose before diving into parameter guidance and quota info. It contains some marketing-style phrasing ('stunning', 'anything'), but every sentence contributes actionable information, making it appropriately sized for an 8-parameter tool.

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?

With no output schema, the description adequately covers the return value (URL + markdown embed), the rendering behavior, the generation pipeline, and quota limits. It also gives recipe-style guidance for common use cases. Minor gaps remain around error handling and image lifetime, but these don't undermine the tool's usability 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?

Schema coverage is 100% (all 8 parameters are described in the schema), so the baseline is 3. The description adds extra practical semantics: 'portrait' for phone/social, 'story' for TikTok/Reels, 'banner' for headers, style examples, negative prompt usage, and count:4 for a variation grid. It doesn't add much for width/height/quality, but the added value is meaningful.

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 identifies the tool as an image generator: 'Generate stunning AI images from any description.' It names the pipeline (Groq enhances, Pollinations renders) and explicitly distinguishes from sibling tools by stating 'image_generate' is the way to generate images in Claude, unlike image_analyze which analyzes 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?

The description gives a strong usage context: 'Claude has no native image generation — this is how you unlock it.' It also provides practical when-to-use guidance for each aspect ratio and style, but it doesn't explicitly mention alternative tools for non-generation tasks or state when not to use it, so it lacks explicit exclusions.

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