Full public details for one product or bundle by its permalink slug (from search-products results) or numeric id: description, pricing, bulk-discount tiers, GST rate, minimum order quantity, stock signal, and page URL.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Product permalink slug or id, e.g. premium-cotton-hoodie |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the full burden of behavioral disclosure. It identifies the tool as returning public details and lists the specific data returned (pricing, GST, stock signal, etc.), which strongly implies a read-only lookup. It does not mention not-found behavior or rate limits, but for a simple retrieval tool this is adequate.
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?
A single dense sentence states the action, input, and complete list of output fields with no filler or redundancy. The key purpose is front-loaded, and every phrase 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?
With only one required parameter and no output schema, the description covers the input origin, accepted forms, and the essential return fields. It could add error-handling or not-found behavior, but for this simple tool the description provides enough context for safe selection and invocation.
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?
The schema already documents the sole parameter with an example, but the description adds important semantics: the slug is a permalink from search-products results and can also be a numeric id. This extra context about parameter provenance and accepted forms goes beyond the bare 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 opens with "Full public details for one product or bundle" — a specific verb-resource-scope statement. It clarifies the input as a permalink slug from search-products results or a numeric id, and enumerates the covered fields, clearly distinguishing this from sibling tools like search-products or calculate-bulk-price.
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 says the slug comes from search-products results, indicating that this tool should be used after a search to retrieve full details for a single product. It does not explicitly list exclusions or alternative conditions, but the intended context is clear.
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 action or resource: product discovery vs pricing vs orders vs meetings vs support. While get-company-info, get-site-info, and get-guide all provide reference material, their scopes are clearly separated (verified facts vs FAQ/how-it-works vs published articles). No two tools appear to do the same thing.
All tool names follow a consistent verb_noun pattern in snake_case: book-, cancel-, reschedule-, get-, search-, list-, request-, track-, reorder-, create-. Even exceptions like my-orders and my-invoices fit a possessive pattern that is predictable. No mixed conventions or vague verbs.
24 tools is on the high end but appropriate for the breadth of this server's scope: product catalog, pricing, meetings, orders, invoices, support, guides, company info, and SEO. Each tool fills a specific niche, and none feel redundant. It is slightly heavy but not overwhelming for the domain.
The tool surface covers the core workflows well: product search/details/pricing, meeting booking/cancel/reschedule, order viewing/tracking/reordering, quotes, complaints, callbacks, invoices, guides, and company information. A minor gap is the absence of a direct 'place new order' tool, but request-quote and reorder handle the necessary paths, and other interactions (e.g., complains) have clear entry points.
