Phase 1 of 2 in the purchase flow. Convert a cart (or inline items + customer) into a checkout. Customer name, email, and phone are required. Returns checkout_id. No payment link is minted yet — call complete_checkout for that. Use update_checkout to correct customer details before finalising.
| Name | Required | Description | Default |
|---|---|---|---|
| items | No | ||
| cart_id | No | Either cart_id or items required | |
| customer | No | ||
| payment_method | No | Default 'yoco' |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description discloses key behaviors: returns checkout_id, does not mint a payment link, and requires customer name/email/phone. It also frames the tool as a preliminary step, setting expectations for subsequent actions. Some side effects (e.g., cart impact) are not described, but the provided context is substantial.
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 four sentences, each serving a purpose: purpose, conversion, requirements/return, and next steps. It is front-loaded with the primary action and phase, with no filler.
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 create operation with no output schema, the description covers workflow, return value, and required fields. It lacks details on error conditions and effects on cart, but given low-to-moderate complexity and schema availability, it is adequately 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?
The description clarifies that either cart_id or items must be supplied, and specifies required customer fields, complementing the schema. It does not detail the shape of items or payment_method default, but schema covers those. The description adds meaningful semantic context beyond the 50% schema coverage.
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's role as Phase 1 of a 2-phase purchase flow, converting a cart or inline items into a checkout. It distinguishes itself from sibling tools like complete_checkout and update_checkout, making the purpose unambiguous.
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?
Explicitly says when to use: to create a checkout, and when not: payment link minting requires complete_checkout. It also points to update_checkout for correcting customer details, giving clear guidance on alternatives.
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.
Most tools have distinct purposes, but the presence of three search tools (search_catalog, search_products, lookup_catalog) and legacy tools (create_order, submit_enquiry) creates minor overlap. Descriptions help differentiate, but an agent might initially confuse them.
All 26 tool names follow a consistent verb_noun snake_case pattern (e.g., cancel_cart, configure_product). No mixed cases or irregular verbs are present.
26 tools is slightly high for a blind shop, but the domain requires many operations (search, pricing, cart, checkout, recommendations, etc.). Some legacy tools could be removed, but the count is still reasonable.
The tool surface covers the full customer journey from product discovery (search, recommendations) to purchase (cart, checkout, payment) and post-purchase (orders, swatches, price match, delivery estimates). No obvious gaps for the stated purpose.