start_checkoutCreate a hosted Cashfree or PhonePe checkout after signed-in browser approval. No payment is captured by this tool.
| Name | Required | Description | Default |
|---|---|---|---|
| coupon_code | No | ||
| payment_mode | No | ||
| payment_method | Yes | ||
| billing_address | No | ||
| confirmation_id | No | ||
| idempotency_key | Yes | ||
| points_to_redeem | No | ||
| shipping_address | No |
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate idempotentHint=true and readOnlyHint=false. The description adds meaningful behavioral context: the checkout is hosted, requires prior browser approval, and does not capture payment. This goes beyond what annotations alone provide and contradicts nothing.
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?
Two short sentences, front-loaded with the core action and followed by a key caveat. Every word earns its place; no filler or repetitive schema 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 8 parameters, 0% schema descriptions, and 2 required fields, this description is incomplete. An agent still cannot determine how to fill idempotency_key, what billing_address or shipping_address mean, how points_to_redeem behaves, or what the browser-approval flow requires. An output schema exists but does not compensate for missing input semantics.
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 0%, so the description must carry parameter meaning, but it only restates the provider enum (Cashfree or PhonePe) and omits explanation for the required idempotency_key, addresses, coupon, points, and confirmation_id. It adds no meaning beyond what the enum already conveys, and it ignores the 'online' payment_method option.
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 and resource ('Create a hosted checkout'), names the supported providers (Cashfree or PhonePe), and adds a prerequisite (signed-in browser approval). The explicit note that no payment is captured clearly separates it from payment-related siblings like retry_payment and resume_payment.
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?
Gives some context ('after signed-in browser approval') and a boundary ('No payment is captured by this tool'), which implies a later payment step. However, it does not explicitly name alternatives or state when not to use this tool versus siblings like resume_payment, retry_payment, or get_checkout_summary.
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 are clearly separated by resource and action (cart, orders, tickets, picks, payments), so an agent can generally select the right one. The only notable ambiguity is resume_payment vs retry_payment, which both describe acting on an unpaid hosted payment attempt with nearly identical wording.
All 29 tools follow a consistent snake_case verb_noun (or verb_preposition_noun) pattern with standard verbs like get, list, create, close, remove, and set. There are no mixed conventions or vague generic names.
At 29 tools this is a heavy surface, but the broad e-commerce scope (catalog, cart, checkout, payment, orders, support, rewards) justifies most of them. A few payment-attempt tools could be consolidated, so it sits at the overbuilt rather than absurdly bloated end.
The set covers the main customer journey from browsing/searching sarees through cart, checkout, payment status, orders, and post-purchase support. Minor gaps exist—for example, no explicit apply_coupon/redeem_points tool or standalone catalogue listing—but agents can work around them with validate_coupon, checkout summary, and search.