Manually update the price on a saved item. Records old and new price for comparison. This is a manual correction, not automatic price tracking.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | The item ID | |
| price | Yes | New current price | |
| reason | No | Why this change was made (shown to user in change history) | |
| source | No | Price update source |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=false, idempotentHint=true, and destructiveHint=false. The description adds useful behavioral context by stating that it 'records old and new price for comparison' and clarifying it is a manual correction, which goes beyond the raw annotation values.
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 three concise sentences, front-loaded with the primary action. Every sentence adds distinct value: what it does, side effect (recording old/new), and a clarification of its scope.
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 mutation tool with full schema coverage and clear annotations, the description is nearly complete. It explains the purpose, the side effect, and the intended context. A minor gap is lack of explicit mention of required fields or prerequisites, but the schema covers those.
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 descriptive parameter details (e.g., 'New current price', 'Why this change was made'). The description adds minimal parameter meaning beyond clarifying that the update writes the new price and preserves the old for comparison, so baseline 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 tool's function: 'Manually update the price on a saved item.' It uses a specific verb ('update') with a specific resource ('price on a saved item') and distinguishes this from automatic price tracking, which separates it from siblings like update_item.
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 for use: it is a manual correction rather than automatic price tracking. While it does not explicitly name alternative tools like update_item for editing other fields, the 'not automatic price tracking' exclusion helps an agent decide when to invoke this tool.
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.
