create_price_alertCreate an email alert on a product's price for the signed-in user. Fires when the product's price changes (any_change) or moves by at least a threshold percentage. This modifies the user's account — only call when they explicitly ask to be alerted or to watch a product's price.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | ||
| thresholdPercentage | No | Only alert on moves of at least this percent; omit for any change |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full transparency burden. It explicitly discloses that this modifies the user's account, requires explicit user consent, and explains the two firing modes. It omits details like duplicate-alert behavior and success response, but the core side effects are clearly stated.
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, front-loaded with the action and resource, and every sentence adds useful context: trigger behavior, side effect, and consent requirement. No filler or redundant restatement of the tool name.
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 two-parameter tool with no output schema, the description covers purpose, trigger conditions, side effects, and user consent. It does not explain slug provenance or success behavior, but these are not critical gaps given the tool's simplicity and the sibling context.
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 only 50%: thresholdPercentage has a schema description, but slug has none. The tool description does not explain what slug refers to or how to obtain it, and it only restates the threshold concept already present in the schema. At this coverage level, the description should compensate but does not.
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 and resource ('Create an email alert on a product's price') and clearly distinguishes this from sibling read/list tools like list_alerts or get_product. It also adds trigger semantics (any_change vs threshold) that make the tool's purpose unmistakable.
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 gives a clear usage condition: only call when the user explicitly asks to be alerted or watch a product's price, and warns that it modifies the user's account. It does not name alternative tools, but the context is strong enough to guide appropriate use.
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.