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

Annotations already declare readOnlyHint=true, destructiveHint=false and idempotency, so the safety profile is known. The description's 'nothing is created' reinforces this but adds little new behavioral detail, and says nothing about result volume or image format.

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?

Front-loaded with the core purpose and kept to a single sentence plus a clarifying clause. The parenthetical examples earn their place; no 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?

A simple read-only gallery tool with no output schema, so the description carries some burden for describing what comes back. It conveys the content type but not count, format, or filtering behavior, leaving gaps an agent might expect filled.

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 baseline is 3, but the description goes further by giving concrete theme examples ('birthday mug for grandma', 'holiday photo', 'cat') that illustrate the intended granularity of the theme parameter. The group parameter is only indirectly covered by 'product for an occasion or theme'.

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 ('shows') and resource ('example pictures for inspiration') and scopes it to product/occasion/theme use cases. An agent can distinguish this from search_products or create_design, though it doesn't explicitly name those siblings.

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?

Implies usage via 'for inspiration' and clarifies the negative case ('existing pictures only; nothing is created'), which helps route away from creation tools. However, no explicit alternative is named, so the agent must infer when to prefer this over search_products.

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