在线产品

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

No annotations are provided, so the description must shoulder the burden. It indicates a read operation but offers no additional behavioral details such as data freshness, rate limits, authentication requirements, or what happens with empty results. The description is too sparse for a tool with no 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 description is a single, focused sentence that conveys the essential purpose and search dimensions. It is concise and front-loaded, with no redundant information.

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 absence of an output schema and annotations, the description should provide more detail. It only partially covers parameter semantics and omits behavior or output structure, making it insufficient for an agent to fully understand the tool's capabilities.

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 low (17%), but the description partially compensates by linking search types (store, ASIN, SKU) to parameters shopIds, searchType, and searchContent. However, the date-related parameters (dateStart, dateEnd, dateType) are not explained, leaving gaps.

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 tool retrieves online product information (Listing/SKU dimension) with search capabilities. It is specific about the verb '获取' and resource '在线产品信息', but does not explicitly differentiate from sibling tool 'sellfox_online_products_v2', which could cause confusion.

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 mentions search by store/ASIN/SKU, providing context for when to use the tool. However, it lacks guidance on when not to use it or how it compares to other tools like sellfox_product_sales or sellfox_online_products_v2, leaving the agent to infer.

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