Fetch images from a ChatGPT conversation

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

Beyond the annotations, it discloses the wait_seconds timing behavior, the STILL RUNNING/QUEUED return state, and the follow-up action with the job_id, which is the information an agent needs to drive this tool. It does not spell out that files are written to disk (readOnlyHint=false despite 'without sending anything'), which would have been helpful given the output_dir parameter.

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 key action and link requirement are front-loaded, followed by usage triggers and return behavior. It is dense but each clause (timeout/retry, earlier chat, wait_seconds, STILL RUNNING) contributes; only the 'Like generate_image' aside slightly compresses two ideas into one sentence.

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?

With five parameters, no output schema, and openWorldHint=true, the description covers the essential return semantics (timeout states, job_id) and the non-generating nature of the call. The gap is that file-writing side effects and the output_dir interplay are only implicit, which matters for a remote-fetch tool.

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 coverage is 100%, so the schema already documents all five parameters thoroughly. The description reinforces wait_seconds' default and explains that aspect_ratio should be re-passed from a generate_image job, but adds little beyond that; the baseline 3 applies.

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 states a specific verb and resource ('Download the generated images of the latest answer in an existing ChatGPT conversation (by its link)') and explicitly scopes it to non-generating retrieval ('without sending anything'), which separates it from siblings generate_image and job_status.

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?

It gives explicit triggers ('when a job timed out or failed... but the chat finished later', 'or to save images from an earlier chat') and routes the agent to job_status when the result is STILL RUNNING/QUEUED, so there is no ambiguity about when to use it or what to do next.

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