Check the status of a checkout session or order.
Use this after the user has completed an escalation step (e.g. payment in the browser) to see if the checkout can now proceed, or to check on a completed order's status.
| Name | Required | Description | Default |
|---|---|---|---|
| checkout_id | Yes | The checkout session ID to check |
| Name | Required | Description | Default |
|---|---|---|---|
| result | Yes |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations provided, the description carries the burden of behavioral disclosure. It implies a read-only operation ('Check the status') and adds valuable context about when to call it, but it does not mention potential side effects, error conditions, or idempotency. There is no contradiction with annotations since none exist.
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 core purpose, then provides usage context. No redundant information or 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 simple one-parameter tool with an output schema, the description adequately covers purpose and usage timing. It does not explain return values, but the output schema handles that. It could explicitly mention alternatives, but that is not essential.
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 schema description for checkout_id is present and covers 100% of parameters. The description references 'checkout session or order' indirectly but adds no new parameter details. Given the high schema coverage, the baseline score of 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 clearly states the tool's function with a specific verb and resource: 'Check the status of a checkout session or order.' It distinguishes from sibling tools like start_checkout and complete_purchase by focusing on status checking.
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 provides explicit usage context: 'Use this after the user has completed an escalation step...' and covers two scenarios (polling for checkout readiness and checking completed orders). It does not explicitly name alternative tools, but the timing guidance is clear.
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.
The tools are mostly distinct: search_products and find_deals overlap somewhat (both search), and compare_prices overlaps with search_products in returning comparison data, but the descriptions clarify the different intents. The checkout lifecycle tools are clearly separated.
All tool names follow a consistent verb_noun snake_case pattern (check_order, compare_prices, complete_purchase, find_deals, search_products, start_checkout, update_checkout_info). No mixed conventions or vague verbs.
Seven tools is well-scoped for a shopping assistant covering search, deals, comparison, and the full checkout flow. Each tool earns its place without redundancy.
The toolset covers the core shopping lifecycle: discovery (search, deals, compare), checkout (start, update, complete), and order status (check). Minor gaps exist such as no explicit cancel checkout or detailed order retrieval, but agents can work around these.
