ghl_product_review_count

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

Beyond the readOnly/idempotent annotations, the description discloses the auth requirement (Sub-Account/location token), the OAuth scope products.readonly, and the API version header, all of which affect whether a call will succeed. It does not, however, explain what the count is grouped by or whether zero-result behaviour differs.

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 first two lines are near-duplicates ('Fetch Review Count as per status' / 'API to fetch the Review Count as per status'), wasting the most prominent position. The endpoint, version, token, and scope lines do earn their place, so it is not bloated overall, just poorly 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?

For a read-only aggregate with no output schema, the description should say what the returned count represents (total, or broken down by rating/status). It covers invocation requirements well but leaves the return value undefined, which is the main remaining gap for a tool named 'count'.

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 coverage is 86%, so the schema already documents altId, rating, and the date/store/product filters; the description adds nothing to those. Worse, the phrase 'as per status' hints at a status dimension that does not exist in the parameters, which could mislead an agent into expecting a status filter.

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 ('Fetch Review Count') for the products/reviews domain, and the endpoint line pins down the exact operation. It is distinguishable from siblings like ghl_product_review_list, but the qualifier 'as per status' is confusing because no 'status' parameter exists in the schema, leaving the exact shape of the result ambiguous.

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?

Usage is only implied: the name and 'count' semantics suggest using this instead of ghl_product_review_list when an aggregate is wanted, but the description never states that contrast or any prerequisites beyond the token requirement. An agent must infer the choice from the tool name alone.

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