products_get_reviews_count

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is known. The description adds no behavioral details beyond the word 'Fetch', which is consistent with read-only. It does not disclose what the response contains (e.g., a single integer, a breakdown by rating) or any API constraints. The description is not contradictory, but it is redundant with the name and annotations.

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 extremely short (one sentence), but that brevity sacrifices clarity. It is not front-loaded with useful information; the phrase 'as per status' is misleading and unexplained. While concise in length, it is under-specified rather than appropriately sized, so structure fails to serve the agent.

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 7 optional parameters and no output schema, the description leaves the agent without essential context. It does not explain what 'status' refers to, what types of counts are returned (e.g., total count, count by rating), or how filters like storeId and productId combine. This is inadequate for a tool with this parameter richness.

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 100%—each parameter has a description. The tool description adds no additional meaning beyond what the schema already provides. Per the baseline for high schema coverage, a score of 3 is appropriate; the description does not enhance understanding of how parameters like altId, rating, or date filters interact.

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 it fetches a review count, but the qualifier 'as per status' is ambiguous—there is no 'status' parameter in the schema. It essentially restates the operation implied by the name and provides no concrete clarification of what specific data is returned. It does not distinguish itself from sibling tools like products_get_product_reviews or products_get_product_store_stats beyond the word 'count'.

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?

There is no guidance on when to use this tool versus alternatives. It does not mention that it is a read-only aggregation, when filtering by rating or date range is appropriate, or when a user should instead call a reviews list endpoint. The absence of any usage context leaves the agent to guess.

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