CDK Bot: lock the current price for a digital product and get USDC payment instructions. Returns a quote_id valid for 5 minutes. After paying, use confirm_purchase with the tx_hash and quote_id.
| Name | Required | Description | Default |
|---|---|---|---|
| chain | No | Payment chain. Use "base-sepolia" for sandbox testing with mock keys. | |
| game_id | Yes | Game ID to get a price quote for |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses that the quote is time-limited (5 minutes) and returns payment instructions. No annotations to contradict. Could mention if any side effects (e.g., creating a lock on inventory), but reasonable for a simple 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?
Two concise sentences, front-loaded with action and resource, no wasted words. Efficiently communicates core functionality and related 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?
Explains return value (quote_id, instructions) and ties to confirm_purchase. No output schema, but adequate for a simple 2-parameter tool. Could mention response format briefly, but not critical.
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 covers both parameters fully (100% coverage). Description adds no extra parameter details beyond the schema, so baseline 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?
Clearly states it locks current price for a digital product and returns USDC payment instructions. Differentiates from sibling tools like confirm_purchase by describing the quote-and-pay workflow.
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?
Provides workflow context: lock price, pay, then use confirm_purchase. Mentions 5-minute validity. Does not explicitly state when to use versus alternatives, but the description implies unique use case.
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.
Each tool has a clear, distinct purpose: browsing filters, searching, getting details, quotes, payment confirmation, order checking, refunds, and reviews. No overlap or ambiguity.
All tool names follow a consistent verb_noun pattern with underscores (browse_filters, check_order, confirm_purchase, etc.), making them predictable and easy to understand.
8 tools cover the essential workflows of a digital product marketplace without being excessive. Each tool serves a necessary step in the user journey.
The tool set covers search, filtering, pricing, payment, order status, refunds, and reviews. Missing a dedicated tool for listing past orders, but the workflow is otherwise complete.
