Get a working Mockup Studio deep link for a product, so the user can upload their logo, position it in the real print zone and download a free mockup — no sign-in needed. Use when someone asks how their logo would look on an item.
| Name | Required | Description | Default |
|---|---|---|---|
| slug | Yes | Product permalink slug or id (from search-products) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the behavioral disclosure burden. It states that no sign-in is needed, that the link is free and working, and what the user can do with it, which sets accurate expectations for a read-only link-generation operation. It does not document errors or edge cases, but the absence of side effects lowers the need for that.
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?
The description is two sentences with no filler. The first sentence front-loads the core deliverable and user value, and the second provides the exact trigger scenario. Every phrase adds information about purpose, workflow, or access requirements.
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 one-parameter, no-output-schema tool, the description is complete: it explains what the user gets (a working deep link), what they can do with it, that no sign-in is needed, and when to invoke the tool. Nothing critical is missing for correct 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?
Schema description coverage is 100%, and the single `slug` parameter is already well documented as 'Product permalink slug or id (from search-products)'. The tool description adds no real parameter detail beyond connecting the slug to 'a product', so the schema is doing the heavy lifting; a baseline 3 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 uses a specific verb ('Get') and resource ('working Mockup Studio deep link for a product'), and clearly distinguishes this from sibling tools like get-product-details by focusing on the interactive mockup link rather than product information. The outcome is concrete: the user can upload a logo, position it, and download a free mockup.
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 use the tool: 'Use when someone asks how their logo would look on an item.' This gives a clear user-intent trigger. It does not mention exclusions or compare directly with alternative tools, but the context is strong enough for an agent to choose this over product-detail tools.
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.
