list_ordersBestellungen des verknuepften Kunden inkl. Status, Zahlstatus und Lieferstatus/Sendungsverfolgung. Erfordert ein via link_account verknuepftes token.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Max. Bestellungen (1-20, Default 10). | |
| suche | No | Optional: nach Auftragsnummer/Artikel filtern. | |
| token | Yes | session_token aus link_account (nach Browser-Login). |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses the auth requirement and outlines the data included (status, payment, delivery). However, it omits details on pagination, error responses, or rate limits. Adequate but not thorough.
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 sentences: first defines the output, second states the prerequisite. No unnecessary words, front-loaded with the key purpose. Extremely concise and well-structured.
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 no output schema, the description partly compensates by naming the status fields included. It covers the prerequisite and basic behavior. Could be improved with default limit and output format, but is largely complete for a listing 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?
Parameter descriptions are fully covered in the schema (100% coverage), so baseline is 3. The tool description does not add extra meaning beyond the schema; it does not reference the parameters or their usage. No enhancement over schema.
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 it lists orders of a linked customer, including status/payment/delivery tracking. The verb 'list' and resource 'orders' are specific, and the tool is distinct from siblings like list_products or list_bestsellers.
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?
No explicit guidance on when to use versus alternatives. The requirement for a token from link_account is mentioned, but there is no discussion of alternative tools or exclusions. Since no other sibling lists orders, usage is implied but not clarified.
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.