Dropshipping MCP Dsers

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

While annotations declare readOnly/idempotent hints, the description adds substantial behavioral context: details the response structure (price_summary object, options array format), explains truncation behavior (values truncated to 10), clarifies field semantics (sell_price vs cost vs compare_at_price), and notes active_rules is always present. Compensates well for missing output schema.

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?

Information-dense with zero waste. Front-loaded purpose statement followed by mode comparison, field definitions, and specific usage guidance. Every sentence conveys critical information about response structure, parameter interaction, or usage context. Excellent structure for a complex tool with multiple modes.

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 the complex nested response structure and lack of output schema, the description comprehensively documents return values: details price_summary object fields, variant table columns for each mode, options array structure with truncation behavior, and active_rules. Adequately covers the tool's behavioral surface area.

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 significant semantic value: explains 'compact' is 'lightweight' while 'full' includes cost/supplier data, clarifies that show_all_options should be used before applying option_edits (workflow context), and maps variant_detail values to specific column outputs beyond the schema's basic description.

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 'Reload preview for an import job' with specific verbs and resource. It distinguishes from sibling dsers_product_import by emphasizing this is a reload/preview operation on an existing job (referenced via job_id), not the initial import creation.

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 guidance: 'Use variant_detail='full' when agent needs compare_at or cost columns' and hints at workflow with 'set show_all_options=true for full list'. Could be improved by explicitly stating when to prefer compact vs full mode or mentioning this should be used after import creation but before final confirmation.

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