Dropshipping MCP Dsers

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

Annotations cover safety profile (readOnly, destructive, idempotent). Description adds significant behavioral context: return field structure (compensating for no output schema), price conversion logic (cents to dollars), and pagination quirk (minimum 20 items, client-side truncation).

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?

Every sentence earns its place: purpose, prerequisite, return format, price conversion, scope clarification, alternative reference, pagination note. No filler. Front-loaded with core purpose.

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?

Comprehensive for tool complexity. Compensates for missing output schema by documenting all return fields. Covers prerequisites, sibling differentiation, and pagination behavior. With annotations present, description provides complete operational picture.

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?

Despite 100% schema coverage, description adds valuable context: store_id provenance (from dsers_store_discover) and page_size behavioral constraint (truncation if < 20). Elevates above baseline 3.

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?

Description opens with specific verb 'Browse' + resource 'products already pushed to a store', clearly distinguishing from siblings. Explicitly contrasts with dsers_import_list ('waiting to be pushed') and links to dsers_store_discover for prerequisites.

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 prerequisite ('Requires store_id from dsers_store_discover') and clear alternative tool reference ('To see products waiting to be pushed, use dsers_import_list'). States exact scope (products 'already pushed').

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