Create a new collection

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, so the safety profile is covered structurally. The description adds a concrete rate limit (100 requests / 10 seconds per shop), which is genuine behavioral context, but it says nothing about the effect of creating a duplicate collection, permission requirements, or the confirm/account gating mechanism implied by the schema.

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 blocks with no filler sentences. Leading with the rate-limit aside before the purpose is slightly awkward ordering, but the text is tight and complete for 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?

With annotations carrying destructiveness, openness, and non-idempotency, and no output schema to explain, the description's main job is minimal. It still leaves the mutually exclusive body variants (payload, payload_file, and flat flags) and the confirm requirement unexplained, which is a real gap for a 7-parameter tool with a nested required payload.

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 71%, and the schema itself documents account, confirm, payload, payload_file, and offerIds. The description only restates name/description/product list, adding essentially no meaning beyond the structured fields, and ignores the payload-vs-payload_file alternation entirely.

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 ('Creates a new collection') and names the fields it accepts (name, description, optional product list). An agent can tell it is a create operation, but the description never names or contrasts with siblings such as update_collection, list_collections, or get_collection.

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?

There is no guidance on when to call this versus update_collection or the other collection tools, and no prerequisites stated. The only operational note is a rate limit, which is a constraint rather than usage direction.

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