CDK Bot: list all available platforms, devices, regions, and languages for filtering digital product searches. Call this first to know what filter values are valid.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden. It accurately describes a read-only listing operation with no side effects. The behavior is clear and consistent with the tool's purpose.
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-load the core functionality and usage guidance. No unnecessary words; every sentence adds value.
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 no parameters and no output schema, the description adequately covers purpose and usage. It mentions what it lists but could imply the output format more explicitly, though not essential.
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?
The tool has zero parameters, and schema coverage is 100%. The description does not need to add parameter information since none exist. Baseline score of 4 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?
The description clearly states the tool lists all available platforms, devices, regions, and languages for filtering digital product searches. It uses specific nouns and distinguishes itself from sibling tools like search_games.
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 explicitly instructs 'Call this first to know what filter values are valid,' providing clear when-to-use guidance. It implies use before search tools but doesn't explicitly exclude scenarios.
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.
