全部产品一览

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so the safety profile is covered by structured data. The description usefully adds that results come back as in-store price ranges, but for a tool that returns ALL products it says nothing about result size, truncation, or pagination limits — a meaningful omission for a full-catalog listing.

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?

A single well-formed sentence with the resource up front and the benefit clause last; no filler or repetition. It could have spent that second clause on a routing hint, but nothing is wasted.

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 an output schema present, return values need not be described, and annotations cover safety. What is missing for a catalog-wide enumeration tool is any caveat about volume, pagination, or cost of an unfiltered call — the one thing an agent must know before invoking it.

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%, and the schema already documents both sort (with per-value semantics) and has_price_only. The description adds nothing about either parameter, so the baseline 3 applies — the schema does all the work here.

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 names a specific verb+resource (列出所有可比价的 AI 产品/SKU) and even states the payload (店内到手价区间), which is more concrete than the title. It distinguishes itself from search_products mainly through '全部' and '门店覆盖范围', but never names the sibling explicitly, so the contrast is implied rather than stated.

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 trailing clause 方便了解全站覆盖范围 hints at the intended use case (a coverage/site-wide overview rather than a targeted lookup), which is more than nothing. However it never says when NOT to use this tool or points to search_products / get_lowest_price for filtered or single-item queries, so an agent must infer the routing.

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