create_cartLegt einen vorbereiteten Warenkorb an und gibt eine Checkout-URL zurueck. WICHTIG: schliesst KEINE Bestellung ab — der Kunde muss die URL im Browser oeffnen und dort Login, Altersnachweis und Zahlung durchlaufen.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Positionen (max. 50). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description bears full responsibility for behavioral disclosure. It discloses the core behavior (creates cart, returns URL) and explicitly states it does not complete orders. However, it lacks details such as whether the operation is idempotent, if there are side effects on existing carts, or any rate limits. The most critical behavioral trait (no order completion) is covered, but more context would improve transparency.
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 two sentences long, no filler. The first sentence delivers the core purpose and return value; the second sentence adds critical context. Information is front-loaded and every word earns its place.
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?
Given the tool has only one parameter and no output schema, the description adequately explains what the tool does, what it returns (checkout URL), and what it does not do. It also provides post-usage context (customer must open URL and go through steps). No additional information seems necessary for an agent to correctly invoke this tool.
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% with one parameter ('items') described in the schema as 'Positionen (max. 50)' and nested properties for article ID and quantity. The tool description does not add additional meaning beyond the schema, so baseline score 3 is appropriate.
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 clearly states the verb 'anlegen' (create) and resource 'Warenkorb' (cart), and specifies the return value 'Checkout-URL'. There are no sibling tools related to cart creation, so it is well-distinguished.
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?
The description explicitly notes when to use the tool (creating a prepared cart returning a checkout URL) and importantly clarifies what it does NOT do ('schliesst KEINE Bestellung ab') and the subsequent steps the customer must take (login, age verification, payment). This provides clear usage boundaries.
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.
Each tool targets a distinct function: inventory checks, cart creation, product search, order management, loyalty, support. No overlap among search_products, list_products, and get_product; similarly, list_orders and request_address_change are unique.
All tools follow a verb_noun pattern (e.g., check_availability, create_cart, link_account) with consistent snake_case and English verbs, even though the shop is German. No mix of conventions.
19 tools is slightly above the typical 3-15 range for a focused server, but the number is justified by the breadth of shop functionality (product browsing, orders, cart, loyalty, guides, support). Not excessive.
Covers core shopping flows: product discovery, cart creation, order tracking, and account linking. However, missing tools for cart modification (add/remove items), order cancellation/returns, and checkout. These gaps may cause agent failures.