edit_image_conversation

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

The description reveals statefulness via previous_response_id, a key behavioral trait, and implies iterative dependency. However, it does not discuss other behaviors like error states, side effects, or the meaning of the action enum, which are left uncovered.

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 concise sentence with no wasted words, effectively front-loading the key differentiator. It could be slightly expanded to include parameter hints without losing conciseness.

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 (7 parameters, nested objects, no output schema), the description is too brief. It omits information about return values, parameter interactions, and usage patterns beyond statefulness, leaving the agent underinformed.

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 0% schema description coverage and 7 parameters, the description adds meaning only for previous_response_id by explaining its role in statefulness. Other parameters like partial_images, input_image_mask, and output remain undefined, failing to compensate for the schema's lack of descriptions.

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 explicitly states 'Multi-turn iterative image editing', clearly distinguishing from sibling tools like edit_image (likely single-turn) and generate_image. The mention of 'stateful by previous_response_id' further clarifies the specific use case.

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 usage for multi-turn editing through statefulness but does not explicitly contrast with alternatives like edit_image or provide conditions for when not to use this tool. No exclusions or guidance on prerequisites are given.

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