refine_image

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 only states that it refines with modifications, but omits critical side effects such as whether the original is replaced, whether a new image is returned, or what happens if no last image exists. This is a meaningful gap for a tool that mutates prior state.

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 that is front-loaded with the verb and resource. Every word earns its place, with no redundancy or filler.

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 simple one-parameter tool, the description is functionally adequate but lacks key contextual details like the effect on the previous image and prerequisites. It doesn't explain the behavior fully, but the schema and simplicity make it minimally viable.

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?

The input schema has 100% description coverage for the sole parameter 'refinement' with a clear description. The tool description adds no extra semantic value beyond what the schema already provides, so a baseline of 3 is appropriate.

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 uses the specific verb 'Refine' with the clear resource 'the last generated image', distinguishing it from sibling tools like generate_image (creates new) and prepare_image (likely prepares). The phrase 'with modifications' further clarifies 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 phrase 'the last generated image' clearly implies this tool should be used after an image has been generated, providing contextual guidance. It doesn't explicitly name alternatives or state when not to use it, but the context is sufficiently clear for a tool with this simple role.

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