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

Beyond the annotations (readOnlyHint=false, destructiveHint=false), the description discloses that the tool makes zero network requests and that each output row is enriched with stable identity, freshness, evidence gaps, review priority, and a human action. This adds meaningful behavioral context without contradicting the 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?

The two-sentence description is dense but efficient: the first sentence states purpose, the second covers output behavior, the no-network guarantee, and pricing. No filler, but the second sentence is long and packs many clauses; still appropriately sized for the tool's complexity.

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?

For a tool with a large nested schema and no output schema, the description captures the core workflow (compare snapshots), key output enrichment, and the critical constraint (no network requests). The schema's root description handles the one-of condition and legacy productUrls, so the tool-level description remains a solid high-level guide.

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% for all parameters, so the schema already documents fields, types, and constraints. The description adds only a high-level summary of compared attributes (price, MOQ, stock, supplier, badge, promotion) but does not explain parameter syntax or relationships beyond what the schema already provides. Baseline 3 applies.

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 uses a specific verb ('Compare') with a precise resource ('buyer-owned, merchant-authorized, or licensed 1688 offer exports') and enumerates the compared attributes (price, MOQ, stock, supplier, badge, promotion changes). It clearly distinguishes this tool from sibling China-focused monitors by targeting 1688 supplier data specifically.

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?

The description explicitly defines the intended input type (authorized offer exports) and the operational context (no login, scraping, API, or URL fetch), which implies offline use with buyer-provided data. It does not explicitly name alternatives or state when not to use, but the clarity of purpose and constraints provides strong usage guidance.

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