import_photos

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

Annotations declare readOnlyHint=false and destructiveHint=false, and the description is consistent with that (it writes files locally). The description adds real behavioral context the annotations do not carry: it strips EXIF/GPS metadata on save and enforces a hard 1–20 attachment ceiling. It stops short of saying where files land on disk.

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?

Two sentences, zero filler. The core action and its critical input constraint are both front-loaded.

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?

An output schema exists, so return values need not be described, and the safety profile is covered by annotations. The remaining shortfall is minor: it does not state the local save destination or what happens when an item in a batch fails to download.

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 0%, so the description must compensate, and it does: it establishes that the photos array must contain genuine ChatGPT file objects with real download URLs, not paths or fabricated links, and caps the array at 20 items (a limit absent from the schema). It leaves the individual PhotoFile fields (file_id, file_name, mime_type) unexplained, so it does not fully close the gap.

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?

States a specific verb (download/save) plus resource (ChatGPT photo attachments), along with two distinguishing traits: the 1–20 batch bound and EXIF/GPS stripping. Nothing here resembles the sibling tools (get_status, prepare_listing, publish_listing), so the agent can separate it immediately.

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?

"Requires actual file objects from ChatGPT, never sandbox paths or invented URLs" is an explicit precondition that rules out the most likely misuse mode. It gives clear context but names no alternative tool and no when-not-to-use case beyond that constraint.

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