Search catalog for available matches by product name. No match does not imply unavailability everywhere; verify details on the linked page.
Find available catalog matches for a product name. No match does not mean unavailable everywhere. Confirm precise material, configuration, price and retailer stock on the linked page.
| Name | Required | Description | Default |
|---|---|---|---|
| product | Yes |
Changes observed during successful MCP inspections.
v0.3.0Input schema / additionalPropertiesAdded value: +falseInput schema / properties / api_keyRemoved value: -{
- "description": "Optional API key for authenticated access.",
- "type": "string"
-}Input schema / properties / product / descriptionRemoved value: -"Product name or URL slug to check availability for (e.g., 'Chris Reeve Sebenza', 'hinderer-xm-18')"Input schema / properties / product / maxLengthAdded value: +120Input schema / properties / product / minLengthAdded value: +1v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuine value beyond them: results are approximate catalog matches, absence of a match is not global unavailability, and precise material/configuration/price/stock must be verified on the linked page — important interpretive context for an open-world lookup.
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 short sentences, front-loaded with the core action before the caveats. Nothing is redundant, though the final sentence about confirming details on the linked page is slightly tangential to invoking the tool.
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 single-parameter read-only lookup with rich annotations and no output schema, the description supplies what is missing: the nature of the matches and how to interpret a negative result. It stops short of describing what a match entry contains beyond implying a linked page.
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?
Only one parameter exists ('product') and the schema documents no constraints at all (0% coverage, no description). The description compensates by clarifying the parameter is a product name used for matching, which is the key semantic an agent needs; a higher score is capped by the absence of any guidance on name format or ambiguity handling.
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?
States a specific verb ('Find') and resource ('available catalog matches for a product name'), so an agent knows this is a catalog-match lookup rather than a pure inventory check. It is clear on its own, but it never distinguishes itself from the sibling search_products, which sounds like it could also return catalog matches.
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 usage (checking availability by name) and adds a useful interpretation caveat that a no-match result is not proof of universal unavailability. However, it gives no explicit when-to-use guidance versus search_products or the other siblings, leaving the choice to inference.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.