Edit image from text + input image(s)

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 save-to-disk behavior, provider limitations (impossibl unsupported), per-provider image count constraints, default model/quality tiers (non-top-tier defaults), and the provider-selection decision flow. Also discloses the memory/ask-user behavior. It doesn't mention auth/permission needs, but the structured schema already documents API key configuration requirements.

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 a single tight sentence that packs the essential purpose. However, significant guidance lives inside the provider parameter's schema description rather than the main description, which means the core description alone is minimal. It's not bloated but arguably shifted more responsibility to schema fields than ideal for a 5.

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?

The schema covers all parameters at 100% coverage and documents the tricky provider-selection decision flow. The description handles the main purpose well. Gaps: no output schema describing what gets returned beyond 'saves result to disk,' and details around multiple input images handling are only lightly covered. For a moderately complex 8-param tool with full schema coverage, this is reasonably complete.

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 schema itself documents all 8 parameters. The description adds value by clarifying provider-specific limits (Grok 1 image, Gemini/GPT-image multiple) and noting impossibl doesn't support editing at all — details beyond the raw schema. However, most other params (size, quality, filename, aspect_ratio) are adequately documented in schema and the description doesn't add further meaning beyond that 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 clearly states the action: 'Edits or transforms one or more input images according to a text prompt,' naming three provider options and explicitly the save-to-disk behavior. It distinguishes itself from siblings by addressing input-image transformation rather than generation, and it explicitly notes impossibl.com is unsupported, adding clarity about scope.

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 and schema give explicit guidance: when multiple providers are configured, check memory for a stored preference, otherwise ask the user which provider to use. It also explicitly states when NOT to use the tool ('impossibl.com does not support image editing at all — do not select it for this tool'), and the input_images param description notes Grok supports 1 image vs. Gemini/GPT-image multiple, guiding provider selection.

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