Save a product to YOUR wishlist on this merchant for later. Idempotent: saving the same product again updates its note and keeps the original save time. Scoped to your own agent identity. REQUIRES IDENTITY: Facet KYA as Authorization: Bearer <kya>.
| Name | Required | Description | Default |
|---|---|---|---|
| note | No | Optional short note. No personal data. | |
| product_id | Yes | The product id to save. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description fully carries the behavioral disclosure burden. It explicitly explains idempotency ('updates its note and keeps the original save time'), scoping ('Your wishlist', 'your own agent identity'), and authentication requirements ('REQUIRES IDENTITY: Facet KYA as `Authorization: Bearer <kya>`'). This goes well beyond a simple 'saves a product' statement.
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?
Three concise, information-dense sentences. Every sentence provides unique value: what it does, idempotency behavior, and auth requirement. No filler or repetition of schema details.
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?
The tool is simple, but the description covers all necessary operational context: purpose, side effects (idempotent note update), identity scope, and auth header. It doesn't explain return values, but no output schema exists and the mutation behavior is clear. Sibling tools provide additional context for alternatives.
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%, so the baseline is 3. The description adds semantic value by explaining idempotent behavior for repeated product_id submissions—specifically that the note updates while save time is preserved. This goes beyond the schema's basic field descriptions and helps the agent understand the net effect of calling the tool.
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 uses a specific verb+resource: 'Save a product to YOUR wishlist on this merchant for later.' It clearly distinguishes from sibling tools like wishlist_remove and wishlist_list by focusing on the add action with the purpose 'for later.'
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 provides clear context: it's scoped to the agent's own identity and requires a specific auth token. While it doesn't explicitly say 'use wishlist_remove instead' or list when-not-to-use, the sibling context and 'save for later' make the intended use obvious. No exclusions are given, but the identity requirement is a meaningful usage constraint.
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.
Most tools map to a distinct lifecycle step, and the detailed descriptions separate discovery, cart, checkout, payment, order, and wishlist concerns well. However, get_product and lookup_catalog are largely the same lookup by identifier, discover_products and search_catalog overlap across scope, and update_checkout is actually a read-only no-op.
The set overwhelmingly follows a verb_noun pattern: create_cart, get_checkout, cancel_checkout, complete_checkout, search_catalog. Minor deviations are the wishlist_* resource-first subgroup and the misleading update_checkout, which does not perform an update.
At 23 tools, this sits at the heavy end of the range, though the broad commerce lifecycle does justify substantial surface area. The count is inflated by redundant product lookup tools and a no-op update_checkout, so a more trimmed set in the low-to-mid teens would be healthier.
The server covers the full shopper lifecycle well: discovery, product lookup, cart, checkout, payment, order placement, order read, refunds, and wishlist. Gaps are minor and workable, such as update_checkout not actually supporting updates and no explicit order-cancellation path once a checkout is complete.
