list_items

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

No annotations are provided, so the description carries the full burden. It only mentions 'GET', which implies read-only behavior, but it does not disclose pagination behavior, default sorting, filtering scope, or any access requirements. The description adds minimal value beyond the schema.

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, direct sentence that includes the action and endpoint. No words are wasted, and it is front-loaded with the primary purpose. Despite being terse, it is appropriately concise for a simple list tool.

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?

The schema fully documents parameters, and the description provides a clear purpose and endpoint. However, there is no output schema or behavioral details, and the lack of differentiation from sibling tools leaves gaps in understanding what exactly this list returns and when to use it. It is minimally adequate but not complete.

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 input schema provides descriptions for all 8 parameters (e.g., 'upc', 'page', 'keyword'), resulting in 100% schema coverage. The description itself adds no parameter information, so the baseline of 3 is appropriate.

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 a list operation for items with the Chinese phrase '取得商品列表' and includes the HTTP endpoint 'GET /v1/items'. However, it does not differentiate from sibling tools like list_products or list_item_selection, 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?

There is no guidance on when to use this tool versus alternatives. The description lacks any context about typical use cases, exclusions, or relationships to sibling tools, so an agent cannot decide between list_items and similar list functions.

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