Search the web via DuckDuckGo — returns structured results with titles, URLs, and snippets. 5 credits.
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | Search query | |
| api_key | Yes | Your DACIX API key (dacix_sk_...). Get one with store_register. | |
| num_results | No | Results to return (1-20) |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Discloses output format (titles, URLs, snippets) and credit cost, but no annotations exist; additional details like idempotency or error handling would improve transparency.
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?
Single sentence plus cost note is extremely concise and front-loaded with essential 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?
For a simple search tool, the description covers output and cost; missing details like result ordering or language/region defaults, but overall sufficient.
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 descriptions cover all parameters (100%), but the tool description adds no extra meaning beyond what the schema already provides, so baseline score 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?
Description clearly states it searches the web via DuckDuckGo and returns structured results, effectively distinguishing it from sibling tools like web_crawl or web_fetch.
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 usage for general web search and mentions cost, but lacks explicit guidance on when to use versus alternatives or constraints like rate limits or required permissions.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.