Create a pre-filled 1-click checkout link for the customer with their selected items and delivery info.
| Name | Required | Description | Default |
|---|---|---|---|
| items | Yes | Array of items to purchase | |
| customer_name | No | Customer first name | |
| customer_email | No | Customer email address | |
| customer_phone | No | Customer phone number (e.g. 0761234567) | |
| customer_surname | No | Customer surname | |
| delivery_address | No | Delivery street address |
Changes observed during successful MCP inspections.
Input schema / properties / customer_email / descriptionPrevious value: -"Customer email address [Optional: omit to use server default filter]."New value: +"Customer email address"Input schema / properties / customer_name / descriptionPrevious value: -"Customer first name [Optional: omit to use server default filter]."New value: +"Customer first name"Input schema / properties / customer_phone / descriptionPrevious value: -"Customer phone number (e.g. 0761234567) [Optional: omit to use server default filter]."New value: +"Customer phone number (e.g. 0761234567)"Input schema / properties / customer_surname / descriptionPrevious value: -"Customer surname [Optional: omit to use server default filter]."New value: +"Customer surname"Input schema / properties / delivery_address / descriptionPrevious value: -"Delivery street address [Optional: omit to use server default filter]."New value: +"Delivery street address"Input schema / properties / items / descriptionPrevious value: -"Array of items to purchase [Required: non-empty valid value must be supplied]."New value: +"Array of items to purchase"Input schema / properties / customer_email / descriptionPrevious value: -"Customer email address"New value: +"Customer email address [Optional: omit to use server default filter]."Input schema / properties / customer_name / descriptionPrevious value: -"Customer first name"New value: +"Customer first name [Optional: omit to use server default filter]."Input schema / properties / customer_phone / descriptionPrevious value: -"Customer phone number (e.g. 0761234567)"New value: +"Customer phone number (e.g. 0761234567) [Optional: omit to use server default filter]."Input schema / properties / customer_surname / descriptionPrevious value: -"Customer surname"New value: +"Customer surname [Optional: omit to use server default filter]."Input schema / properties / delivery_address / descriptionPrevious value: -"Delivery street address"New value: +"Delivery street address [Optional: omit to use server default filter]."Input schema / properties / items / descriptionPrevious value: -"Array of items to purchase"New value: +"Array of items to purchase [Required: non-empty valid value must be supplied]."Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden but only implies a mutation and that a link is produced. It says nothing about whether the customer is charged, whether the link expires, auth requirements, or what happens if customer/delivery fields are omitted for a 1-required-parameter tool.
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 well-formed sentence that front-loads the action and the output artifact with no filler. It is efficient, though it is arguably under-specified rather than optimally concise for a 6-parameter creation tool.
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?
The schema fully documents the six parameters, so input semantics are covered, but with no annotations and no output schema the description should explain the side effects and return value (the link) more concretely. It gives the shape of the result but not enough for an agent to call this safely in edge cases.
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%, so every parameter is already documented in the schema. The description's mention of 'selected items and delivery info' loosely maps to the items and delivery_address fields but adds no format or constraint detail beyond that, so the baseline 3 applies.
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 ('Create') and a concrete artifact ('pre-filled 1-click checkout link') and lists the inputs it carries (items, delivery info). This is clearly distinguishable from every sibling (list_products, check_delivery_coverage, track_order_status), though it never names them explicitly.
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 never says when this tool should be used, what must be verified first (e.g., checking delivery coverage or sourcing product IDs), or what the alternative flows are. Only inference from the phrasing 'selected items and delivery info' hints at context; the reference to list_products lives in the schema, not the description.
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.