Begin an agent-initiated droplinked checkout for a SKU. Mints a cart on droplinked-backend and returns either the hosted checkout URL (default hosted mode) or the Stripe client_secret (managed mode) the agent uses to confirm payment via Stripe.js.
| Name | Required | Description | Default |
|---|---|---|---|
| mode | No | hosted | |
| buyer | Yes | ||
| skuId | Yes | ||
| shopId | Yes | ||
| quantity | Yes | ||
| returnUrl | No | ||
| paymentMethod | No | stripe |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations indicate this is a write operation (readOnlyHint=false) and not idempotent, and the description honestly discloses the side effect of minting a cart. It adds transparency about the two return modes and the Stripe.js flow. No contradiction with 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?
Two sentences, front-loaded with the action and return types. Every clause adds value, with no redundant or vague phrasing. Excellent conciseness for a tool with moderate complexity.
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 description covers the essential flow, side effects, and return values, which is enough for an agent to invoke the tool correctly in most cases. However, it omits details about buyer object requirements and other parameters, and has no output schema to fill the gap. Slightly more explanation would make it 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 description coverage is 0%, so the description must carry the burden of explaining parameters. It only clarifies the 'mode' parameter and mentions SKU, but leaves shopId, quantity, buyer object fields, returnUrl, and paymentMethod unexplained. The agent must infer their purpose from names alone.
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 uses a specific verb ('Begin') and resource ('droplinked checkout for a SKU'), immediately clarifying the tool's function. It clearly distinguishes from siblings by focusing on initiating checkout rather than managing cart lines or processing payments, and it explains the two output modes.
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 gives clear context: use this tool to start an agent-initiated checkout, then confirm payment via Stripe.js in managed mode. It does not explicitly state when _not_ to use it (e.g., for adding items to cart or finalizing payment), but the mode explanation provides practical usage guidance.
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.
Many tools have overlapping purposes, such as find_inventory, search_products, list_shop_products, and get_product all dealing with product discovery/retrieval with subtle differences. Similarly, verify_brand_attestation and get_brand_attestation_status could be confused, as could get_trust_dossier and get_underwriting_signals. The sheer number of verification and lookup tools makes it difficult to pick the right one without careful reading.
The cart tools use a dot-separated camelCase convention (cart.addLine, cart.updateLineQuantity), while the rest use snake_case with varied verbs (find_, get_, list_, search_, verify_, request_, quote_, etc.). This mixing of conventions and inconsistent verb choices (e.g., find_inventory vs search_products vs list_shop_products) makes the tool names unpredictable.
With 38 tools, this server is heavily overloaded. The guidance suggests 25+ tools is too many, and this server exceeds that threshold. While the domain spans commerce, trust attestations, and lending, the count is excessive for a coherent single-server toolkit.
The tool surface is extremely broad, covering cart management, checkout, product discovery, trust verification, and lending workflows. However, there are notable gaps: no cart retrieval or order history, no revoke/update for attestations, and some key lending tools (quote_credit_terms, report_repayment) are scaffolded but not yet functional, creating dead ends.
