CDK Bot: check the status of a purchase order. Provide wallet_address to retrieve the product key. Pending orders are automatically polled for fulfillment.
| Name | Required | Description | Default |
|---|---|---|---|
| order_id | Yes | Order ID (UUID) from a previous purchase | |
| wallet_address | No | Buyer wallet address. Required to retrieve the product key. |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, description discloses polling for pending orders and wallet_address requirement for key retrieval. Lacks explicit statement on side effects, but reasonably transparent.
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 purpose, no superfluous content. Efficient and clear.
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?
Covers core functionality and polling behavior. Could mention error cases or expected response, but no output schema exists to complement. Sufficient for a simple tool.
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 already describes both parameters fully (100% coverage). Description adds that wallet_address is required for product key, which repeats schema info. Baseline 3 applies.
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 checks purchase order status and retrieves the product key, distinguishing it from sibling tools like confirm_purchase or request_refund.
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?
Implies use after purchase for status checking and key retrieval, but no explicit when-not-to-use or alternatives list. Context from sibling names helps differentiate.
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.
