stability_image_to_image

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

With no annotations, the description must convey behavioral traits. It only says 'Transform', omitting details like whether the operation is destructive to the source image, cost implications, rate limits, auth requirements, or the effect of key parameters like strength. For a tool with 9 parameters and 22% schema coverage, this is insufficient.

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 sentence with no wasted words. However, for a tool with 9 parameters, it could include more essential information without becoming overly verbose.

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 complexity (9 parameters, no output schema, low schema coverage), the description is far from complete. It does not mention required parameters, default values, output format, or how to obtain engine_id, leaving agents with significant 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?

Schema description coverage is only 22% (only image_url and strength have descriptions). The tool description adds no parameter explanations, failing to compensate for the many undocumented parameters (e.g., api_key, prompt, engine_id, etc.).

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 ('Transform an existing image') and the input ('using a text prompt') with the provider ('Stability AI'). It distinguishes from sibling tools like stability_text_to_image (text-to-image) and stability_upscale (upscaling), making the purpose unambiguous.

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 provides no guidance on when to use this tool versus alternatives (e.g., stability_text_to_image) or prerequisites such as obtaining an engine_id or API key. It lacks context for effective decision-making.

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