Update a 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 largely covered. The description contributes the concrete rate limit (100 req/10s per shop), which is genuinely new context, but it does not disclose that supplying offerIds replaces the collection's product set or that the operation is non-idempotent.

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 waste, though the rate-limit line is placed ahead of the purpose statement, which slightly buries the front-loaded 'what it does'. Still efficient and appropriately sized.

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, 8-parameter mutation with no output schema, the description covers the basic mutation surface and rate limit but omits replace-vs-merge semantics for the product list and the meaning of confirm. Adequate but with clear gaps an agent would want 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 description coverage is 75%, so the schema handles most parameter documentation (payload, payload_file, confirm, collection_id). The description only restates the updatable fields and ignores the payload/payload_file mutual exclusion and the confirm flag, adding little beyond structured data — the baseline 3 applies.

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?

The description states a specific verb and resource plus the three mutable fields (name, description, product list), so the agent knows exactly what changes. It does not explicitly distinguish itself from near-name siblings like update_collection_products or update_collection_availability, so it falls 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?

There is no statement of when to use this tool versus its siblings (update_collection_products, update_collection_availability, create_collection) and no prerequisites or exclusions. Only a rate-limit note is given, which is operational context rather than usage guidance.

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