Generate or edit an image

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

With only openWorldHint provided, the description carries the behavioral burden and adds real value: it discloses that the result is written to an output directory and that the call is billed to the Modelflare balance by actual usage. It does not cover authentication/permission needs or failure behavior, but the cost and side-effect disclosure is substantive.

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?

Two compact clauses, front-loaded with the core action before the billing note, with no filler. The edit-mode distinction is placed early where it is most actionable.

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?

For a 4-parameter tool with a nested passthrough object and no output schema, the description usefully states where output lands and how billing works, covering the main gap left by the missing return schema. It does not warn about model-specific field requirements in the nested parameters object, but the schema covers that.

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 75%, so most parameters are already documented; the description only reinforces edit=true and the list_models source for model. It adds no meaning for prompt or the nested parameters passthrough object, so it does not compensate beyond the schema baseline.

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 names a specific verb+resource (generates/edits an image) and splits the two modes via the edit=true flag, which is precise enough to act on. It does not explicitly contrast with siblings like create_video, but the resource is distinct enough that confusion is unlikely.

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?

It states that edit=true switches to the edit route and that the model ID comes from list_models, implying a prerequisite lookup. However there is no explicit when-to-use/when-not guidance, no mention of the create_video sibling, and no conditions under which generation versus editing should be preferred beyond the boolean flag.

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