CDK Bot: get detailed information about a specific digital product (game key, gift card, DLC) including price, activation instructions, and delivery time. Use the game_id from search_games results.
| Name | Required | Description | Default |
|---|---|---|---|
| game_id | Yes | Game ID (UUID) from search results |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations provided, so description carries full burden. Mentions included information (price, activation instructions, delivery time) but does not disclose behavioral traits like read-only, idempotency, or any side effects. Adequate but not thorough.
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: first defines the tool's purpose and outputs, second provides input sourcing guidance. No redundant or missing information.
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?
Given the tool's simplicity (one parameter, no output schema, no annotations), the description adequately covers purpose and input. Could specify output structure, but not required.
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 coverage is 100% with a single parameter game_id already described. Description adds value by specifying the source ('from search_games results'), which aids understanding beyond the schema's 'from search results'.
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?
Description clearly states 'get detailed information about a specific digital product' with examples (game key, gift card, DLC). It distinguishes from siblings like search_games (list) and get_price_quote (price only).
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?
Explicitly instructs to 'Use the game_id from search_games results', providing a clear workflow. Does not list when not to use, but context from siblings implies alternatives (e.g., check_order for orders).
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.
