get_reorder_linkReturn the reorder URL, product URL, and a copyable procurement spec for one catalog SKU or handle. Use for repeat-buy and procurement handoff workflows.
| Name | Required | Description | Default |
|---|---|---|---|
| sku | No | Packrift SKU such as 1066, MFL1295, or LL251WR. | |
| handle | No | Packrift product handle if SKU is unknown. | |
| source_context | No | Optional short context label, such as reorder or procurement. |
Changes observed during successful MCP inspections.
Input schema / properties / analytics_contextRemoved value: -{
- "description": "Internal QA context for synthetic evals.",
- "type": "object"
-}Input schema / properties / source_context / descriptionPrevious value: -"Optional analytics context, e.g. ai_agent_reorder or mcp_reorder."New value: +"Optional short context label, such as reorder or procurement."Input schema / properties / suppress_analyticsRemoved value: -{
- "description": "Internal QA flag. When true, do not record an AI-sales reorder event.",
- "type": "boolean"
-}Input schema / properties / analytics_contextAdded value: +{
+ "description": "Internal QA context for synthetic evals.",
+ "type": "object"
+}Input schema / properties / suppress_analyticsAdded value: +{
+ "description": "Internal QA flag. When true, do not record an AI-sales reorder event.",
+ "type": "boolean"
+}Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnly, idempotent, and openWorld hints. The description adds value by detailing the exact output (reorder URL, product URL, copyable procurement spec) and the one-item scope, without contradicting the annotations.
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, front-loaded with the primary function, and includes only relevant usage guidance. No redundant or filler content.
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 tool with 3 optional parameters and no output schema, the description provides a good overview of returned data and use cases. It does not cover edge cases like missing SKU/handle, but the annotations and schema fill in most gaps. Overall, reasonably complete.
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% with parameter descriptions, providing a baseline of 3. The description adds meaning by implying that sku and handle are alternative identifiers for a single item, which is not explicitly stated in the schema. It also clarifies the tool operates on one SKU or handle.
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 clearly states the tool returns a reorder URL, product URL, and procurement spec for a single SKU or handle. It uses a specific verb and resource, and the mention of 'one catalog SKU or handle' distinguishes it from sibling tools like create_cart_url or get_bulk_quote_link.
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 'Use for repeat-buy and procurement handoff workflows,' providing clear context. However, it does not specify when not to use the tool or mention alternatives, so it falls short of a 5.
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.