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

No annotations are provided, so the description carries full behavioral burden. It implies a read-only search but omits auth requirements, rate limits, pagination, and return behavior. Additionally, the platform-specific parameter guidance conflicts with the schema, which only defines a single 'id' parameter.

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, front-loaded sentence with no wasted words. The parenthetical parameter note is compact, though its mismatch with the schema reduces its practical value.

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?

With no annotations and no output schema, the description should provide more behavioral and return context. The parameter guidance is inconsistent with the schema, leaving the agent without a clear way to map platform-specific IDs to the single 'id' field.

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%, so the baseline is 3. However, the description introduces shop_id and seller_id parameters that do not exist in the schema (which only has 'id' and '_token'), creating confusion rather than adding meaningful semantic clarity.

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 states a specific verb (search) and resource (on-sale products in JD/Taobao shops), which distinguishes it from item-level tools like ecommerce_item. It does not explicitly name a sibling tool, so it falls short of a 5.

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?

It gives platform-specific parameter instructions (JD uses shop_id; Taobao uses seller_id+shop_id), which is useful context. However, it does not explain when to choose this tool over alternatives like ecommerce_item or search_1688, leaving usage implied.

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