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

Annotations declare the safety profile (not read-only, not destructive, not idempotent), so the description's job is to add context — which it does: changes take effect at once on every product, no approval flow, members-only auth, and a 12-picture cap including the cover. It does not explain what happens to existing images not mentioned or any failure/response behavior, which keeps it short of 5.

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 operation, then limits, then semantics, then id sources, then auth — a sensible order with little waste. The 'rikma or personal' aside and the trailing docs URL add marginal words, but nothing is redundant enough to obscure the call.

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 5-parameter mutation tool with no output schema and full annotation coverage, everything an agent needs is present: required ids, per-slot semantics, limits, ordering, and the auth requirement. Nothing essential about invoking it correctly is missing.

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, and the description genuinely adds meaning beyond the schema: gallery ordering is significant, the 12-picture total includes the cover, an empty array clears the gallery but preserves the cover, and variant pictures are optional per-variant. It still does not say what happens for an absent coverId, which is the one 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 and resource ('Set a product's pictures'), enumerates exactly which slots are set (cover, gallery, per-variant), and implicitly separates itself from the proposal-based siblings in the same family. An agent can distinguish it from proposeProductEditTool or setProductCategoriesTool without opening the schema.

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?

Gives explicit operating instructions: omit galleryIds to leave the gallery untouched, sourced ids come from getUploadSession, uploadMediaFromUrl or getRikmaProduct, and membership is required. It also states the key decision rule versus the propose* siblings — this applies immediately with no proposal.

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