AliExpress / Alibaba / Accio Product Import

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

Beyond the annotations, the description discloses important behavioral traits: it explains the difference between single and batch responses, the deduplication behavior on re-import ('DSers finds the existing draft (no duplicate)'), and the deprecation of job_id. It also clearly indicates that imports create entries (not read-only) while warning about update operations. No contradictions with 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 lengthy but well-structured and information-dense. It front-loads the core purpose and then details response modes and alternative tools without redundancy. The use of all-caps section headers (e.g., 'SINGLE RESPONSE', 'BATCH RESPONSE') improves scannability, though slightly verbose for a tool description.

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 tool's complexity (16 parameters, single/batch modes, no output schema), the description is remarkably complete. It explains what the return previews look like in both single and batch modes, how to handle lost job IDs, and the distinction between this tool and its siblings. No output schema exists, so the description fully compensates by detailing response formats.

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 input schema already provides 100% description coverage for all 16 parameters, so the baseline is 3. The description adds value by clarifying parameter relationships and usage patterns, such as 'Provide source_url (single) or source_urls_json (batch)' and 'Optionally apply rules at import time via rules_json or flat params.' However, the marginal gain is limited since the schema already explains each parameter in detail.

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 clear, specific action: 'Import product(s) from supplier URL(s) into the DSers import list and return a preview.' It also names the exact supported platforms (AliExpress, Alibaba, Accio.com), distinguishing this tool from siblings like dsers_product_preview and dsers_product_update_rules by explicitly pointing to them for alternative use cases.

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 explicit guidance on when to use this tool vs alternatives: 'To UPDATE rules on an existing import, use dsers_product_update_rules instead' and 'Use dsers_product_preview for individual details.' It also advises on batch vs single usage and how to handle expired/lost job IDs, giving clear context and exclusions.

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