create_collection

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

With only openWorldHint in annotations, the description adds some behavioral context: the collection is created empty and the name is sent as the collection title. However, it omits permissions, duplicate-name behavior, idempotency, and visibility or sync implications, so it only partially carries the disclosure burden for a create mutation.

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?

The description is front-loaded and mostly concise: three useful sentences covering creation, fields, and workflow. The trailing '[#ff2c5e]' token is irrelevant noise that slightly undercuts conciseness.

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 relatively simple create tool with no output schema, the description covers the core action, key fields, and next steps. Still, missing workspace parameter semantics and mutation caveats leave meaningful gaps given minimal annotations and 0% schema description coverage.

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 0%, so the description must compensate. It explains name and description, and 'in a store' loosely implies store_uuid, but the workspace parameter is never mentioned and no format or source details are added for store_uuid.

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 with scope: 'Create a new (empty) collection in a store.' It distinguishes the tool from update_collection, delete_collection, get_collection, and list_collections, and names the follow-up tools add_products_to_collection and sync_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?

It gives a clear creation workflow: provide a name and optional description, then use add_products_to_collection and sync_collection. It does not explicitly state when not to use this tool or contrast it with update_collection, but the intended usage context is clear.

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