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

Beyond readOnlyHint/openWorldHint annotations, the description adds that the display caps at 12 images, that it includes download buttons, and that it 'Spends nothing' — a cost-safety fact the annotations do not convey. It does not describe pagination or what happens with more than 12 matching images.

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?

A single sentence front-loads the core action and cap, then the two modes, then the cost reassurance. No filler and nothing buried.

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 read-only, two-optional-parameter tool with an output schema, the description covers purpose, both modes, and cost. The only minor gap is not noting the 12-image limit's behavior when more ids would otherwise apply, but the schema's maxItems handles that.

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 description coverage is 100%, so both parameters are already documented, including the default of 6 and the 12 maximum. The description restates the interaction between generationIds and the latest fallback but adds no syntax or format detail beyond the schema, so 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?

Uses a specific verb ('Shows') plus the resource ('finished images side by side with download buttons') and states the two retrieval modes (by generation_id, or latest). It implicitly separates itself from get_generation_status by saying 'finished images', though it never names the sibling explicitly.

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 'generation_id values from completed get_generation_status results' implies the workflow point at which to call this tool (after generation completes) and the fallback when no ids exist. It stops short of explicit when-not guidance or naming alternatives such as get_generation_status or list_reference_images.

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