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

Annotations already declare readOnly, idempotent, non-destructive, and closed-world, so safety is covered. The description adds the returned field set, but says nothing about pagination behavior, ordering, or limits despite having paging parameters.

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 compact sentences with the core purpose front-loaded; the '[read]' tag is redundant with readOnlyHint but costs little. No filler sentences.

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?

Covers what the tool returns and why you would use existing images, which is adequate given no output schema. It is incomplete on pagination/result-set behavior, which matters for a listing tool with page/per_page parameters.

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 0% for the two parameters (page, per_page), so the description bears the burden and provides nothing about paging semantics, defaults, or ordering. An agent must infer behavior entirely from parameter names.

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+resource (list the merchant's finished pictures) and enumerates the key returned fields (image_id, image_uuid, title, output url). It also implicitly contrasts with generation siblings via 'use one instead of making a new picture', though no sibling is named 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?

'Use one instead of making a new picture when it fits the topic' is guidance about reusing the returned assets, not about when to call list_images versus create_image, list_videos, or render_image. The when-to-use context is only implied.

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