get_price_historyThe complete verified price-change history of a product, beyond the public 10-change window. Requires the user's PriceTrack account. Call when the user asks how a product's price evolved over time, or for changes older than the recent ones get_product shows.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| limit | No | Max changes, default 100 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations declare readOnlyHint=true, and the description adds significant behavioral context: it requires the user's PriceTrack account, notes the history is 'verified', and clarifies it goes beyond the public 10-change window. This goes beyond the annotation without contradicting it, though it doesn't mention rate limits or pagination.
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, front-loaded with the core purpose, and then provides usage guidance. Every sentence earns its place with no fluff or repetition.
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 (2 params, no output schema). The description covers purpose, usage, auth requirement, and scope. It doesn't explicitly describe the return format, but 'price-change history' sufficiently implies a list of changes. Given the low complexity, this is nearly complete.
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 50% (only 'limit' has a description). The description doesn't directly explain the 'slug' parameter, but the phrase 'of a product' implies it. The 'limit' parameter's schema description is sufficient. No additional parameter meaning is provided by the description.
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 retrieves the complete verified price-change history of a product, explicitly distinguishing it from the limited public 10-change window and from what get_product shows. This is a specific verb+resource with clear sibling differentiation.
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?
It gives explicit when-to-use guidance: 'Call when the user asks how a product's price evolved over time, or for changes older than the recent ones get_product shows.' This also names the alternative tool (get_product), making the usage context unambiguous.
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 has a clear, distinct purpose: searching, fetching details, comparing, history, recent changes, alerts, stack, and list. No two tools appear to overlap in functionality, making selection unambiguous.
Most tools follow a verb_noun pattern (compare_products, create_price_alert, get_price_history, get_product, get_stack, list_alerts, search_products), but recent_price_changes breaks the pattern as an adjective_noun. Minor inconsistency but still predictable.
8 tools is well-scoped for a price tracking service, covering search, detailed lookups, comparisons, history, alerts, and user-specific views without unnecessary bloat.
Core workflows are covered: search, view details, compare, get history, set alerts, and view tracked stack. Missing update/delete alert operations and a way to manage tracked products directly, but these are minor gaps agents can work around.