Get detailed product and variant information after search_products identifies a product and merchant. Use before purchase when the user needs details, options, price, or variant information.
| Name | Required | Description | Default |
|---|---|---|---|
| site_slug | Yes | ||
| product_id | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It indicates a read operation by using 'get' and 'information', but it does not explicitly state that the tool has no side effects, nor does it mention error behavior, availability constraints, or data freshness. Adequate for a simple retrieval but leaves some safety implications implicit.
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 fluff. The core action is front-loaded in the first sentence, and the usage condition follows immediately. 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?
For a simple two-parameter read tool with no output schema, the description conveys the essential purpose, workflow position, and trigger conditions. It does not explain return structure or error cases, but those are less critical for a straightforward retrieval. The main gap is the lack of explicit parameter definitions, which is already captured in parameter_semantics.
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 0%, so the description must compensate. It implies that site_slug and product_id are the merchant and product identifiers produced by search_products, but it never explicitly maps each parameter. This gives some contextual meaning beyond the bare schema, yet leaves the exact roles of the two parameters under-specified.
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 states a specific verb and resource: 'Get detailed product and variant information'. It also situates the tool in a clear workflow ('after search_products identifies a product and merchant') and distinguishes it from siblings like search_products, add_to_cart, and create_checkout by limiting its role to pre-purchase detail retrieval.
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 explicit usage context: use after search_products and before purchase when the user needs details, options, price, or variant information. It does not explicitly name alternatives to avoid, but the workflow positioning and 'after search_products' precondition provide clear guidance for when this tool applies.
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.
Most tools target distinct steps in the purchase flow, and descriptions clarify the intended sequence. The main overlap is search_catalog being a legacy alias for search_products; check_inventory and get_product have slight overlap but are distinguished by availability checking versus detailed product info.
All tool names follow a consistent verb_noun snake_case pattern such as search_products, get_product, create_cart, add_to_cart, and create_checkout. The naming pattern makes the workflow stage and action immediately clear.
With 8 tools, the surface is well-scoped for a shopping-and-checkout flow: discovery, product details, inventory, cart creation/modification, cart review, and checkout handoff. The redundant search_catalog alias is minor and does not make the set feel bloated.
The core path is complete: search → product details → inventory check → create cart → add to cart → get cart → create checkout. Minor gaps such as removing or updating cart items are missing, but the essential purchase workflow is fully supported.