list_products

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

No annotations are provided, so the description carries the behavioral burden. It conveys that the tool returns product line and price-band information, and the verb '查' implies a read-only query. Yet it doesn't disclose details like response format, ordering, pagination, or whether all products are included.

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 one short, front-loaded sentence with no filler. Every word contributes to conveying the tool's core purpose.

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 one-parameter list tool, the description is adequate: it identifies the input and the nature of the output. However, it doesn't explain how the distilleryId should be obtained (e.g., via list_distilleries) or precisely what 'price band' means, and there is no output schema to fill that gap.

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?

The schema fully documents the single parameter distilleryId as '酒厂 id', and the description references '某家酒厂' but adds no new meaning beyond that. With 100% schema coverage, the baseline of 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 '查某家酒厂的产品线与价格带' states a specific action (query) and resource (a distillery's product line and price band). It clearly distinguishes from siblings like list_distilleries (which lists all distilleries) and get_distillery (which returns distillery details).

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 implies the use case: call it when you need the product lineup and prices for a specific distillery. However, it provides no explicit guidance on when not to use it or how to choose between this and siblings like search_whisky or get_distillery.

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