get_productFetch a single canonical product by its canonicalProductId, with current per-retailer offers. Descriptive only. Returns an error_v1 body with NOT_FOUND if the id is unknown.
| Name | Required | Description | Default |
|---|---|---|---|
| canonicalProductId | Yes | Canonical product id (CUID) from search results. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, so the description's 'Descriptive only' reinforces safety. The description adds value by specifying the error response (NOT_FOUND) for unknown IDs and mentioning offers are included, which goes beyond what annotations provide.
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 sentences with no unnecessary words. The first sentence conveys the core purpose and output scope; the second adds error handling. Every word earns its place.
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?
Without an output schema, the description covers the main return value (product with offers) and error case. However, it does not detail the structure of a successful response, which might be needed for complex processing. Still adequate for a simple lookup.
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%, and the parameter is well-described in the schema as 'Canonical product id (CUID) from search results.' The description references the parameter but adds no additional semantic detail beyond the schema.
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 action ('Fetch'), the resource ('canonical product'), and the context ('with current per-retailer offers'). It also specifies that the operation is descriptive only, leaving no ambiguity about what the tool does.
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 the tool should be used when you have a canonicalProductId and need product details, but it does not explicitly contrast with sibling tools like search_offers (which might search by criteria) or list_calibers. No when-not-to-use guidance is provided.
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 targets a distinct resource and action: market statistics, product lookup, caliber directory, retailer directory, and offer search. There is no meaningful overlap between get_product and search_offers because one is a direct single-item fetch and the other is a multi-result search.
All tools follow a consistent verb_noun pattern: get_ for single-item fetches, list_ for enumerations, and search_ for queries. The naming is uniform and predictable.
Five tools is well-scoped for a read-only market data service. Each tool covers a necessary capability without redundancy or bloat.
The tool set provides full coverage for its descriptive market-intelligence purpose: listing reference data (calibers, retailers), searching/fetching products and offers, and retrieving aggregate price statistics. No obvious CRUD or operational gaps exist because the service is explicitly read-only.