search_productsSearch products across all Coal merchants. Filter by name, max price, or tag. Returns a Markdown product grid with images. Use this when looking for something specific like "find a figurine under $1".
| Name | Required | Description | Default |
|---|---|---|---|
| tag | No | Filter by product tag | |
| search | No | Product name search (fuzzy) | |
| maxPrice | No | Maximum price in USD |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint, openWorldHint, and idempotentHint, covering the safety profile. The description adds valuable behavioral context by specifying the return format (Markdown product grid with images), which is not evident from the schema or annotations. It does not contradict annotations.
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?
Three short sentences, each earning its place: what it does, return format, and a usage example. No redundancy or filler.
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 read-only search tool with no required parameters and no output schema, the description covers the core behavior, filters, return format, and a usage case. It could mention potential limits or pagination, but the simplicity and annotations make it sufficiently complete.
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 description coverage is 100%, so the schema already fully documents all three parameters. The description repeats the filters (name, max price, tag) but adds little beyond the schema. It aligns with the baseline for complete schema coverage.
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's function: searching products across all Coal merchants, with specific filter options. It distinguishes from siblings like discover_merchants by focusing on products rather than merchants or other entities.
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 an explicit use case: 'Use this when looking for something specific like "find a figurine under $1"'. This gives clear context for when to use it, though it doesn't explicitly mention alternatives or when not to use it, which would make it a 5.
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.
Several tools overlap in the product discovery and payment status domains. discover_merchants, search_products, and get_merchant_profile all relate to finding products/merchants, though descriptions clarify intended use. Similarly, check_paywall, get_checkout_status, and verify_receipt all deal with payment status/verification, creating potential agent confusion.
Most tools follow a consistent lowercase verb_noun pattern (check_paywall, create_checkout, download_product, get_0g_health, etc.). The one outlier is agent_wallet_status, which is a noun phrase instead of verb-first, but it still uses underscores and fits thematically.
13 tools is within the ideal range and the server covers payments, product discovery, and verification. A few tools like get_0g_health and setup_instructions feel tangential to the core payment flow, making the set slightly heavier than necessary but still reasonable.
The payment lifecycle is well covered: discover/search products, pay via checkout or direct merchant payment, download digital goods, and verify receipts. Minor gaps exist such as no explicit refund or transaction history tool, but agents can work around these by using existing verification and wallet status tools.