Dropshipping MCP Dsers

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

While annotations cover safety profile (readOnlyHint, destructiveHint), the description adds crucial behavioral context: it discloses the three-component return structure (effective_rules_snapshot, warnings, errors) and explains what each contains (adjustments made vs blocking issues). The 'normalize' behavior is also disclosed.

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 efficient segments: action statement, usage context, and structured return documentation. Every clause provides distinct value. No redundant text or tautology.

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?

Compensates well for missing output schema by documenting return values (effective_rules_snapshot, warnings, errors) and their meanings. Establishes clear relationship with sibling tool dsers_product_import. Could mention idempotency explicitly, though covered by annotations.

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% with detailed parameter descriptions (including JSON structure examples and pricing modes). The description references 'rules object' and rule types (pricing, content, images) aligning with schema but does not add semantic information beyond what the schema already provides. Baseline 3 appropriate.

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?

States specific verbs ('Check and normalize') and resource ('rules object') with clear scope ('against provider's capabilities'). Explicitly distinguishes from sibling dsers_product_import by positioning itself as the pre-import validation 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 workflow guidance: use this 'before importing' and specifically references dsers_product_import as the subsequent step requiring error-free validation. Explains the value proposition ('see exactly which ones will be applied').

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