列出收录店铺

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

Annotations already declare readOnlyHint=true and openWorldHint=true, so safety and open-world behavior are covered. The description adds the sort order (cumulative sales) and the filterable dimension, but the enumerated return fields duplicate what the output schema already provides, so it adds only modest context.

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, front-loaded sentence ordered as purpose then scope then filter. It is efficient, though the trailing list of return fields is redundant given the output schema and slightly dilutes the signal.

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?

Both parameters are fully documented in the schema, the output shape is described by an output schema, and the annotations cover the safety profile. The only real gap is the absence of routing guidance relative to sibling list/search tools, which is minor for a simple read-only listing.

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%: the schema documents limit (default 10, max 30) and platform with concrete example values. The description only restates the platform filter and adds nothing on syntax or format, so baseline 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?

States a specific verb (列出) and resource (水獭收录的 AI 订阅店铺), plus the ordering rule (按累计销量) and the shop categories covered (卡网、独立站). An agent can instantly tell this is about shops rather than products, distinguishing it from siblings like search_products and list_all_products.

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 optional platform filter is mentioned ('可按平台筛选'), which implies when to use it, but there is no guidance on when to choose this tool over alternatives such as list_all_products, nor any exclusion or prerequisite. Usage must be inferred from the domain.

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