Dropshipping MCP Dsers

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

Annotations indicate idempotent, non-destructive writes; the description adds crucial workflow context and discloses return values ('job_id, status, visibility_mode') not present in annotations or structured fields. Could explicitly mention idempotency to fully align with annotations, but 'switch between' implies reversibility.

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 sentences with zero waste: purpose (sentence 1), workflow positioning (sentence 2), and return values (sentence 3). Front-loaded with the core action and efficiently structured for an agent parsing the 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?

Adequate for a 2-parameter workflow tool with robust schema coverage and annotations. The description compensates for the missing output schema by listing return values. Would be perfect with explicit mention of idempotency or retry-safety for the workflow context.

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, the schema already documents parameters thoroughly including risk warnings ('SAFE' vs 'RISK'). The description maps 'draft' and 'published' concepts to the visibility_mode parameter, but this adds minimal semantic value beyond the comprehensive schema descriptions.

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 states a specific verb ('Change') with clear resource ('visibility mode of a prepared job') and scope ('before pushing it to the store'). It effectively distinguishes this toggle from sibling import/push tools by positioning it as an intermediate workflow step.

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 temporal guidance ('Call this between dsers_product_import and dsers_store_push') and names specific siblings to establish workflow order. Clarifies the binary choice ('switch between draft and published') and implies this is optional preprocessing before the final push.

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