Generate Image

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

Annotations establish that this is a write operation but non-destructive. The description adds valuable behavioral detail beyond the annotations: it saves PNG/JPG files to KENARI_OUTPUT_DIR, returns absolute paths, and incurs monetary cost. This gives the agent practical expectations about side effects.

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 and front-loaded, covering purpose, mechanism, output location, return value, and cost guidance in two sentences. Every clause contributes useful information without repetition or filler.

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 fully described schema, existing output schema, and annotations, the description supplies the missing operational context: where files go, what is returned, and a prerequisite to check list_media_models. An agent has enough to call this tool correctly without ambiguity.

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 description coverage is 100%, so the baseline is 3. The description adds no parameter-specific meaning beyond what the schema already provides; the cost and model-id guidance mirrors the model parameter description. It does not harm or clarify individual params further.

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 opens with a specific verb and resource: 'Generate image(s)' and gives the exact API endpoint, POST /v1/images/generations. It clearly distinguishes this from sibling tools like edit_image and create_video by stating it creates images and saves them to disk.

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 clear context: use this to generate images, expect per-image IDR costs, and check list_media_models first for model IDs and pricing. It does not explicitly contrast with edit_image or state when to avoid this tool, but the context is strong enough for an agent to select it appropriately.

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