Query China wholesale pricing

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Beyond the readOnly, idempotent, openWorld annotations, the description discloses a behavioral detail: the tool settles ~0.01 USDC per query via x402. It also outlines the output fields. This adds useful context without contradicting the 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?

The description is composed of four short sentences, each delivering a distinct piece of information (purpose, output, usage, cost). It is efficient with no redundant phrasing, though it could be slightly more compact by merging the usage and cost sentences.

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?

The description covers the core aspects: what it does, what it returns, when to use it, and the associated cost. Given the simple query nature and the presence of an output schema, this is sufficiently complete. Minor omissions like pagination or error handling are not critical for a straightforward search/pricing 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?

The JSON schema already provides 100% coverage with clear descriptions for all three parameters (keyword, max_price, category_id). The tool description does not add significant additional parameter semantics beyond what's in the schema (e.g., it doesn't clarify formats or edge cases), so it meets 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 searches for factory-direct wholesale pricing samples by product keyword, specifying the catalog style (1688/Yiwu) and the return fields (MOQ, unit price USD, factory location, supplier verification flags). This is a specific verb-resource-scope combination that distinguishes it from sibling tools (which handle social media notes or payment status).

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 provides a clear usage context ('Use for China sourcing research') and mentions the settlement cost (0.01 USDC). It does not explicitly name alternative tools, but the sibling tools are unrelated domains, so no ambiguity arises. A slight deduction for not stating when not to use the tool.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.