seedream_image_to_image

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

The description indicates the tool modifies images (readOnlyHint false), but it does not elaborate on behavioral traits such as whether the original image is altered (likely a new image is generated), authentication needs, or rate limits. The description adds minimal context beyond what the annotations already imply.

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 that efficiently conveys the tool's purpose and capabilities. It is front-loaded with the core function and avoids fluff, though it could benefit from a slightly more structured format.

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 complexity (many parameters, no output schema), the description covers the essential purpose but lacks details on output format, behavior for optional parameters, and how it fits with sibling tools. It is adequate but not comprehensive.

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?

With schema description coverage at 0%, the description must compensate for parameter meaning, but it only mentions 'text instructions' and 'existing image' without detailing the required prompt and image parameters. Other parameters like size, watermark, etc., are not referenced, leaving the agent without guidance beyond the schema.

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 it performs image-to-image editing based on an existing image and text instructions. It lists specific editing capabilities (style conversion, material replacement, etc.) and implicitly differentiates from siblings like text-to-image by specifying that it works on an existing 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 implies it should be used when editing an existing image with text instructions, but it does not explicitly provide when to use or when not to use this tool versus alternatives like seedream_text_to_image or seedream_multi_image_fusion. No direct comparison or exclusion criteria are given.

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