generate_image

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

With no annotations provided, the description carries the full burden, and it delivers: it discloses the auth requirement (provider API key), the privacy-relevant behavior (image saved locally, not uploaded anywhere), and the Stability-specific quirk (any WxH mapped to nearest supported aspect ratio). No annotation contradiction since none exist.

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 sentences with zero waste: purpose, prerequisite, privacy note, and the provider quirk. The core purpose is front-loaded in the first clause, and every sentence earns its place with distinct, actionable information.

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?

Despite having no output schema and no annotations, the description covers the essential operational aspects: what it does, the required key, where the output lands (locally), and a provider-specific caveat. The one minor gap is that the exact return value (e.g., a local file path) is not spelled out, though 'saved locally' implies it. Moderately complex tool, well covered.

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% and the schema already documents all four parameters including the provider enum, model examples, and size format. The description adds marginal value by mapping providers to named products (fal FLUX, DALL-E 3) and by explaining the Stability size-mapping behavior, but it does not meaningfully expand on the schema's parameter descriptions. Baseline 3 is appropriate.

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?

States a specific verb (generate), resource (image), and method (text description via AI), and names the three providers (fal FLUX, DALL-E 3, Stability). This clearly distinguishes it from the media-generation siblings (generate_video, generate_music, generate_voiceover) and the image-editing siblings (edit_image, animate_image) without ambiguity.

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 states the prerequisite (a provider API key via set_provider_key) and the local-save behavior, which give useful context. However, it never explicitly says when to choose this tool over generate_video, edit_image, or animate_image — the differentiation is only implied by the tool name and the stated purpose, with no explicit exclusions or alternative routing.

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