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

Annotations declare readOnlyHint=false and destructiveHint=true, but the description describes a read-only query operation ('查询商品...'), directly contradicting the destructive annotation. The description also omits any mention of caching, authentication, or side effects, leaving a major behavioral gap.

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, front-loaded sentence that gets to the point quickly. However, it lists several overlapping concepts ('查询商品、购物搜索结果、商品列表'), which is somewhat redundant.

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 tool with seven parameters, no output schema, and annotations that suggest destructive behavior, the description is far too thin. It does not explain return values, caching implications, or why it is marked destructive, leaving the agent without crucial context.

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%, so all seven parameters are fully documented in the schema. The description only mentions offset and filters generically, adding no new semantic detail beyond what the schema already provides.

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 verb (查询) and resource (Bing Shopping 商品/购物数据), making the tool's function clear. It distinguishes itself from general search tools by naming Bing Shopping, though it does not explicitly contrast with sibling shopping tools like google_shopping.

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 provides a trigger condition ('当用户需要...时触发'), which indicates when to use the tool. However, it offers no guidance on when not to use it or how it compares to alternatives like bing_search or google_shopping.

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