search_productsSearch PriceTrack's catalogue of tracked SaaS products by name or description. Call this when the user asks what a SaaS product costs and you need its slug, or when they describe a kind of tool and want priced options. Returns up to 20 matches with slug, category, and starting price. Use get_product with a returned slug for full plan details.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Product name or keywords |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The annotations include readOnlyHint: true, which already communicates this is a safe read operation. The description adds useful behavioral details beyond this, including that it returns up to 20 matches and specifies the fields returned (slug, category, starting price). There is no contradiction with annotations. A score of 5 would require mentioning any rate limits or pagination behavior, which are not present.
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 sentences that front-load the purpose, then usage guidance, then what is returned. No filler words. Every sentence adds value, and the structure is logical.
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?
Given the low complexity (1 parameter, simple string input, no output schema), the description covers the core requirements: what to search, when to call it, what it returns, and the next step (get_product). It doesn't mention sorting order or what happens with empty results, but the limited scope and good annotations make this a minor gap.
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 description coverage is 100% (the single 'query' parameter has a description). The description adds context about what kinds of queries are appropriate (name, description, or tool type description) and hints that results are limited to 20 matches, which adds value beyond the schema. However, it doesn't specify how to format multi-word queries or whether special characters are supported, so a 4 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 it searches PriceTrack's catalogue of tracked SaaS products by name or description, using a specific verb and resource. It distinguishes itself from siblings like get_product (which returns full plan details for a specific slug) and compare_products, so the agent knows exactly what this tool does and how it differs.
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 explicitly states when to call this tool: 'when the user asks what a SaaS product costs and you need its slug, or when they describe a kind of tool and want priced options.' It also provides an alternative: 'Use get_product with a returned slug for full plan details,' which gives clear guidance on when to use this vs. a sibling 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.
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.