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

Annotations already declare readOnlyHint=true, but the description adds access-level behavior (public read vs. logged-in including the caller's own rating) and the important empty-result semantics that prevent fabricated data. It does not cover pagination behavior or result ordering beyond what the schema states.

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?

Purpose is front-loaded in the first clause and the entire definition is a handful of clauses with no filler. However the compressed, punctuation-driven style ('my', '详情→评分') sacrifices some readability for brevity.

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?

With no output schema, the description correctly discloses what comes back (distribution, count, reviews) and how access level changes the result set. Combined with 100% schema coverage and a readOnly annotation, only minor areas like pagination semantics are unaddressed.

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% and all four parameters, including the sort enum and limit bounds, are documented in the schema itself. The description adds no parameter-level meaning such as default sort behavior or cursor expiry, so the baseline 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 and enumerates what is returned (rating distribution, total count, reviews), which distinguishes it from get_product, which the description explicitly says does not include this table. The trailing '详情→评分' is telegraphic and slightly ambiguous about which sibling supplies rating detail, keeping this just below a 5.

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?

Names the alternative for writing ('写评用rate_product'), rules out a sibling ('get_product不含此表'), and adds a when-not-behavioral caveat that empty results are normal and should not be backfilled with official-site reviews. An agent has no inference left to do about which tool to pick.

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