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 critical behavioral context: it decodes specific response flags ('ae_expired' vs 'plan_issue' severity), explains that auth expiration doesn't block imports, and provides workflow constraints ('do NOT retry') that augment the idempotency annotation. Could improve by mentioning cache duration 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?

Information-dense and well-structured: opens with purpose, explains response structure, details specific flags (ae_expired, plan_issue), and closes with explicit workflow instructions. Every sentence delivers actionable information; no filler 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?

Given the lack of an output schema, the description adequately compensates by documenting the return structure (stores with nested fields, rules categories) and explaining domain-specific status flags. It successfully establishes the tool's role as the foundation for sibling operations. Minor gap: no mention of error handling or rate limiting.

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 baseline is 3. The description mentions 'Use the id or name from this response in later calls,' which implicitly validates the parameter's purpose, but does not explicitly discuss the 'target_store' filter behavior or provide examples beyond what the schema already documents.

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 ('Retrieve') and clearly identifies the resources (stores and supported rules). It explicitly distinguishes this tool as a prerequisite for 'all subsequent operations,' clearly positioning it relative to its siblings (import, preview, push, etc.).

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 sequencing guidance ('Call this first'), explains the dependency chain (response contains IDs needed by subsequent operations), and gives clear post-call instructions ('proceed to the next step... do NOT retry discover'). It effectively maps the tool's position in the workflow.

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