ghl_product_review_list

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuinely useful context beyond them: it requires a Sub-Account (location) token, requires the products.readonly OAuth scope, and warns that limit/offset should be used to page through full result sets. Return shape and default page size behavior are still unstated.

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 short and front-loads the operation before endpoint, auth and pagination metadata. The second line ('API to fetch the Product Reviews') is a pure restatement of the title and earns nothing, but the remaining lines are dense and useful.

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?

Auth requirements and pagination guidance cover the main operational gaps for an 11-parameter filtered list. However, with no output schema present, the description says nothing about what a review record contains or how results are ordered by default, leaving the agent to discover the response shape empirically.

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 91%, so the schema already explains altId, ratings, storeId/productId, sort fields and date bounds; the description correctly doesn't repeat them. It only adds that limit/offset exist for paging through complete result sets, which is marginal value over the schema's own parameter descriptions, so the baseline 3 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?

The description names a specific verb (fetch/list) and resource (product reviews) and even cites the underlying REST endpoint GET /products/reviews, so the purpose is unambiguous. It does not, however, distinguish this from adjacent siblings such as ghl_product_review_count or ghl_product_review_bulk_update, so an agent must infer the boundary itself.

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?

Use is only implied: the description says it fetches reviews and that limit/offset should be passed to page through full result sets, which is a useful operational hint for exhaustive retrieval. It never states when to choose this over ghl_product_review_count or other product listing tools, nor any exclusions or prerequisites beyond the token/scope note.

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