Create Image Prompt

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

The description reveals behavior beyond the schema: it optimizes the input into an English prompt, follows 'best practices,' and removes gender/count specifics ('universal'). Since no annotations are provided, this is helpful. It doesn't contradict any annotations.

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, with three short sentences that are front-loaded with the main action. Each sentence contributes distinct value: function, usage suggestion, and output trait. No redundant wording.

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 tool's simplicity (2 params, no output schema), the description covers the core behavior and output. It specifies the model (Flux Klein) and the result (optimized prompt). It could explicitly mention returning the prompt text and note its role as a precursor to generate_image, but these are minor gaps.

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?

The input schema already includes descriptions for both parameters, including the length enum with word ranges and the description parameter with theme/style/mood/setting examples. The tool description adds little new parameter information—it repeats 'theme, style, mood' but omits 'setting' and 'any language'. Thus, schema does the heavy lifting.

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 primary action: 'Generates an optimized English prompt for Flux Klein image generation model based on your description.' This specifies the verb, resource, and target model, differentiating it from sibling tools like generate_image.

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 indicates when to use it: when you have a description and want a well-structured prompt. However, it does not explicitly mention alternatives or when not to use it (e.g., if you already have a prompt, use generate_image directly). The context that it is for the Flux Klein model provides guidance.

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