Dropshipping MCP Dsers

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

Annotations declare read-only/idempotent safety profile. Description adds critical behavioral context: field semantics (no_markup logic, low_stock_warning threshold), return payload structure (lists all 11 fields), and crucial API quirk 'DSers API returns a minimum of 20 items per page. If page_size < 20, results are truncated client-side' which affects pagination behavior.

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?

Efficiently structured: purpose → return fields → field semantics → related tool workflows → sibling differentiation → behavioral note. Every sentence conveys unique information; no repetition of schema defaults or annotation values.

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?

No output schema exists, but description compensates by exhaustively listing all return fields (import_item_id through tags) and explaining business logic (no_markup, low_stock_warning). Complex domain (import staging, variants, push status) is fully contextualized with sibling relationships.

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 coverage is 100% (baseline 3). Description adds value beyond schema by explaining the effective minimum constraint: despite schema allowing page_size=1, the note clarifies that DSers returns minimum 20 items and truncation happens client-side, which is essential for correct pagination handling.

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?

Opens with specific verb 'Browse' + resource 'DSers import list' + qualifier 'with enriched variant data'. Explicitly distinguishes from siblings by defining this as 'the staging area before push' versus 'products already on your store' (dsers_my_products) and 'search for new products' (dsers_find_product).

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 explicit when-to-use: 'This is the staging area before push'. Names specific alternatives: 'To see products already on your store, use dsers_my_products' and 'To search for new products, use dsers_find_product'. Also specifies related workflows: 'Use import_item_id with dsers_product_preview for full details or dsers_product_delete to remove'.

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