Set the pinned "Top Picks" items for a collection (max 3). Pinned items are highlighted on the share page.
| Name | Required | Description | Default |
|---|---|---|---|
| reason | No | Why this change was made (shown to user in change history) | |
| item_ids | Yes | Items to pin, in display order (1st = top) | |
| collection_id | Yes | The collection ID |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses that the operation sets the pinned items (implying replacement), enforces a maximum of 3, and results in sharing-page highlighting. While annotations already mark it as idempotent and non-destructive, the description adds the effect and limit, giving the agent expectations beyond the schema.
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 short sentences with no filler. The first sentence states the action and constraint; the second explains the effect. Highly efficient.
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 simple write operation with a 3-parameter schema and no output, the description covers the purpose, constraint, and effect. It could be slightly more explicit about replacing the entire pinned list, but 'Set' conveys that. Overall sufficient.
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?
All three parameters are fully documented in the schema with descriptions. The description doesn't add parameter-specific details, but since schema coverage is 100%, the baseline of 3 is appropriate. No additional semantics are needed.
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 specific action ('Set the pinned "Top Picks" items') and resource ('for a collection'), with a critical constraint ('max 3'). It distinguishes from sibling tools like add_item or update_collection by naming the unique Top Picks feature.
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 implies when to use it (to set pinned Top Picks) but does not explicitly contrast with alternatives or state when not to use it. The 'max 3' limit provides a usage rule, but there is no mention of exclusions or prerequisites like collection ownership.
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 have clearly distinct purposes with no obvious duplicates. The only potential overlap is between update_item and update_price, but the descriptions clarify that update_price is specifically for manual price corrections with history tracking.
All tool names follow the snake_case verb_noun pattern consistently (e.g., add_item, create_collection, get_item_graph). Slight deviations like add_to_collection and ping are still predictable and conventional.
With 23 tools, the server sits in the heavy range (16-25). While each tool serves a distinct purpose, the count is higher than typical for a shopping-save app and may feel overwhelming, though not excessive.
The tool surface covers full CRUD for items and collections, relations, history, activity, and utilities. Minor gaps exist—such as no dedicated 'move item between collections' tool—but workarounds are possible using existing tools.
