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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuine context beyond that — bilingual English/Chinese matching and the fact that stock/price/suitability are out of scope of the result — but says nothing about result ordering or pagination behavior even though limit/offset exist.

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?

Three short sentences, scope stated first, exclusions second. No filler, and the most load-bearing constraint is front-loaded.

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?

There is no output schema, so the description bears some burden for describing what comes back, and it only tells the agent what is NOT returned. For a search-and-paginate tool with four undocumented parameters, the definition is adequate to start a call but not to predict its results.

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 0%, so every parameter's meaning rests on the description, and it only loosely gestures at 'query' and 'family' via 'name, specification or category'. It says nothing about what limit/offset do, whether family and query can be combined, or what the three enum families actually contain.

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?

Specific verb+resource ('Find HTR Bamboo website products') with the searchable dimensions named (name, specification, category). It does not name the closest sibling get_product, so the boundary between search and retrieve-one is only 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 sentence 'This is not a stock, price or suitability check' is a real exclusion, which is more than most definitions offer. But it never names the alternative (get_product for details, list_product_categories for taxonomy) nor states positive preconditions, so the agent must infer the routing itself.

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