Retrieve detailed information for a single Cole Haan product by its handle. Use the URL slug to fetch structured product data.
Get a Cole Haan product. Returns product detail for one Cole Haan (https://www.colehaan.com) product handle. The storefront URL is fixed server-side; handle is the product's URL slug.
| Name | Required | Description | Default |
|---|---|---|---|
| handle | Yes | Product handle |
Changes observed during successful MCP inspections.
v1.16.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full behavioral burden. It usefully discloses that the storefront URL is fixed server-side and that handle is the product's URL slug, but says nothing about auth needs, rate limits, or what happens with an invalid handle.
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 clauses, front-loaded with the core action, with no filler. Each sentence contributes something (what it gets, what it returns, how the handle is interpreted).
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-entity getter with no output schema and no annotations, the description covers the essentials of what to pass and what comes back. It is slightly thin on failure behavior for an unrecognized handle, but adequate overall.
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 coverage is 100%, but the schema only says 'Product handle', which is circular. The description adds real meaning by defining handle as the product's URL slug and noting the storefront URL is fixed server-side, telling the agent not to pass a full URL.
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 (Get) and resource (a Cole Haan product) and clarifies it returns detail for a single product handle, which cleanly contrasts with the sibling colehaan_products list tool. It does not name that sibling explicitly, so differentiation is implied rather than stated.
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?
Usage is only implied: pass a handle to retrieve one product. There is no explicit when-to-use guidance, no statement of when to prefer colehaan_products or colehaan_search_suggest, and no prerequisites or error conditions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.