Dropshipping MCP Dsers

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

Annotations declare read-only/idempotent safety, while the description adds crucial behavioral context: the state machine lifecycle and the exact return value structure (job_id, status, target_store, etc.) since no output schema exists. It could be elevated to 5 by mentioning polling frequency recommendations or rate limits.

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?

Three tightly constructed sentences each deliver distinct value: purpose statement, behavioral lifecycle, and return value documentation. No redundancy or filler text. Information is front-loaded with the action verb.

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?

For a simple read-only tool with one parameter and comprehensive annotations, the description is complete. It compensates for the missing output schema by inline-documenting return fields, providing sufficient information for successful invocation and result handling.

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?

With 100% schema description coverage (job_id fully documented in the schema referencing source tools), the description appropriately relies on the structured schema. No additional parameter semantics are needed in the text, meeting the baseline for high-coverage schemas.

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 ('Check') and clear resource ('current status of an import or push job'), distinguishing it from sibling tools like dsers_product_import (which creates jobs) and dsers_store_push (which initiates pushes). The scope is precisely bounded to status tracking.

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 status lifecycle ('preview_ready → push_requested → completed or failed') implies a polling pattern and sequential usage context. However, it lacks explicit guidance such as 'Use this after calling dsers_product_import' or warnings about when not to use it (e.g., not for searching products).

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