Dropshipping MCP Dsers

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

Annotations cover read-only/destructive/idempotent status, so the description appropriately focuses on adding pagination behavior ('Use search_after from the response') and response structure ('Results include import_url'). It clarifies the data source (AliExpress catalog) but doesn't mention rate limits or authentication requirements.

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?

Four sentences with strong information density and front-loading. Minor redundancy exists in mentioning 'import_url' twice (sentences 2 and 4), but each sentence serves a distinct purpose: search capability, return value, pagination, and workflow continuation.

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 8 parameters and no output schema in the context, the description compensates effectively by explaining key response fields (import_url, search_after) and the complete workflow lifecycle from search to store push. It provides sufficient context for an agent to use the tool correctly without additional documentation.

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%, establishing a baseline of 3. The description reinforces the mutual exclusivity of keyword vs image_url and mentions search_after for pagination, but doesn't add syntax details, format constraints, or semantic explanations beyond what the schema already provides.

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 opens with a specific verb ('Search'), clearly identifies the resource ('DSers product pool (AliExpress supplier catalog)'), and specifies the dual search modalities ('keyword or by image URL'). It distinguishes itself from sibling tools by focusing on the discovery phase versus import/push operations.

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 maps the tool's position in the workflow chain by naming three sibling tools: 'directly imported via dsers_product_import', 'use dsers_import_list to browse', and 'dsers_store_push to push'. This provides clear when-to-use guidance relative to alternatives.

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