create_listCreates an empty private list (e.g. Narozeniny, Nová kuchyň) in the signed-in person's account; add products with add_to_list. At most 50 lists per person.
| Name | Required | Description | Default |
|---|---|---|---|
| name | Yes | The list's name, e.g. Narozeniny (1 to 80 characters). | |
| locale | No | BCP 47 locale for human-readable strings, e.g. "en", "cs", "sk". Defaults to the country's default locale. |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description adds value beyond the annotations: the list starts empty, is private to the signed-in account, and is capped at 50 per person — a quota the annotations do not express. It does not clarify what is returned on success or what happens at the cap, keeping it below a 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?
One tight sentence front-loads the verb, resource, and scope, then appends the follow-up action and the quota. No filler.
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?
Covers purpose, follow-up flow, privacy, and the quota, which is sufficient for a simple two-parameter create tool with full schema coverage and no output schema. Only the return value/shape of the created list is left unstated.
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% and both parameters are fully documented in the schema, including length bounds and locale format. The description's examples (Narozeniny, Nová kuchyň) merely echo the schema's example, adding no new semantics.
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 ("Creates an empty private list") plus the scope ("in the signed-in person's account"), and gives concrete naming examples. It is clearly distinguishable from siblings like list_my_lists, update_list, and delete_list.
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?
Explicitly routes the follow-up step to add_to_list and states the 50-list cap, which tells the agent when creation will fail. It lacks an explicit "to see existing lists use list_my_lists" style exclusion, but the operational context is clear.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.