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

No annotations are provided, so the description must carry the behavioral burden. It explicitly says 'Read-only', which is helpful, and lists return fields, but omits rate limits, pagination, or what happens with invalid/expired IDs. For a read-only lookup of a finite resource, this is adequate but not rich.

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?

One dense sentence front-loads the platform and operation, then parameters, then returns, then a safety tag. Zero waste.

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 single-parameter lookup with no output schema and no annotations, the description covers what it returns (price, coupon, monthly sales, commission, affiliate click_url), the parameter format and limit, and the read-only nature. Missing only error/edge-case behavior and when to prefer alternatives, which are minor for this tool.

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 0% and the single parameter is undocumented in the schema. The description adds crucial semantics: it is a string of num_iid(s), comma-separated, up to 40. That covers format, plural batch nature, and a hard limit—compensating well for the missing schema description.

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?

States a specific verb+resource: retrieving Taobao item details by num_iid, and distinguishes from siblings like cps_jd_goods_search by naming the platform (Taobao) and the exact identifier (num_iid). An agent can tell this apart from other search/detail tools.

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?

Implicitly guides usage by mentioning batch lookup (up to 40 comma-separated IDs) for product cards, but never states when to use this vs cps_smart_search or get_goods_detail, nor any exclusions or prerequisites.

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