Set collection products

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

Annotations already declare destructiveHint=true and openWorldHint=true, so the safety profile is covered. The description adds two things beyond that: an explicit rate limit (100 req / 10s per shop) and the 'full list' replacement semantics, which implies existing products not in the list are removed. Worth noting: 'sets the full list' reads as idempotent while idempotentHint is false, a mild inconsistency rather than a direct contradiction.

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 short sentences with no filler. The rate limit is front-loaded before the purpose statement, which is slightly odd ordering for a tool-selection decision, but the description is otherwise tight and earns its length.

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 destructive 6-parameter mutation with nested objects and multiple body-passing mechanisms (offerIds, payload, payload_file) and no output schema, the description leaves the agent to reconcile the overlapping input paths and the confirm/account requirements from the schema alone. It is minimally adequate given full schema coverage, but a destructive replace operation would benefit from stating what gets removed.

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 every parameter including offerIds, collection_id, account, confirm and payload_file is already documented in the schema. The description restates the offerIds meaning ('product IDs') but adds no syntax, format, or relationship detail (e.g., how offerIds, payload.offerIds and payload_file interact). Baseline 3 for schema-covered parameters.

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: 'Sets the full list of product IDs in the collection.' The word 'full' conveys replacement semantics, which distinguishes it in spirit from get_collection_products, update_collection and update_collection_availability. It does not name or explicitly differentiate from those siblings, so it stops short of a 5.

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?

No guidance on when to use this instead of update_collection (metadata), update_collection_availability, or get_collection_products. The only contextual note is a rate limit, which is not usage selection guidance. The agent must infer from the name that this is the mutation path for collection membership.

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