Browse DSers Import List

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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true, and openWorldHint=false. The description adds valuable behavioral context beyond annotations: explains the staging area nature, minimum 20 items per page API behavior with client-side truncation, and how to interpret specific fields (no_markup=true, low_stock_warning). No contradiction with annotations.

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?

Well-structured with front-loaded information about what the tool returns, followed by field explanations, usage guidance, and behavioral notes. Every sentence adds value with zero wasted words. The description efficiently covers multiple aspects in a compact format.

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 tool's complexity (list browsing with specific field interpretations), the description provides complete context: detailed return field explanations, behavioral notes about API pagination, clear guidance on when to use versus siblings, and next-step actions. No output schema exists, but the description thoroughly documents what's returned.

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 description coverage is 100%, so the schema already fully documents both parameters (page and page_size). The description adds some context about the minimum 20 items per page behavior when page_size < 20, but doesn't provide additional parameter semantics beyond what's in the schema. Baseline 3 is appropriate when schema does the heavy lifting.

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 clearly states the verb ('browse') and resource ('DSers import list') with specific scope ('with enriched variant data'). It distinguishes from siblings by explicitly mentioning dsers_my_products for products already on store and dsers_find_product for searching new products.

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?

Explicit guidance is provided on when to use this tool ('staging area before push') versus alternatives: use dsers_my_products for products already on store, dsers_find_product for searching new products. Clear context about what this tool provides versus other options.

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