products_get_product_reviews

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

The annotations already declare readOnlyHint, openWorldHint, and idempotentHint, so the safety profile is covered. However, the description adds no behavioral detail beyond that—no mention of pagination, default limits, filtering behavior, or the nature of the returned data. Given the rich annotations, the bar is lower, but the description still contributes nothing beyond the name itself.

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 terse—just three words. While it is front-loaded and free of fluff, it is under-specified rather than concise. It provides only the barest clause and forces the agent to rely entirely on the schema for any operational detail, which is not enough for a tool with 11 parameters.

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 tool with 11 parameters, no output schema, and multiple filtering options, the description is far too sparse. It omits any explanation of what a product review result looks like, how pagination works, which filters are most useful, or any edge cases. The annotations cover safety but not operational context, leaving the agent without sufficient information to correctly compose a request without inspecting the schema in depth.

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?

The input schema covers all 11 parameters with descriptions (100% coverage), so the schema carries the full semantic weight. The description offers no additional parameter context, but the baseline of 3 applies because the schema already documents each parameter thoroughly, including enums and defaults.

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 clearly states a specific verb ('Fetch') and resource ('Product Reviews'), making its primary function unambiguous. It does not explicitly differentiate itself from sibling tools like 'products_get_reviews_count' or 'products_bulk_update_product_review', but the name and wording sufficiently convey that it retrieves review records rather than counts or modifies them.

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 related alternatives (e.g., getting a review count, updating or deleting reviews). The description provides no context about scenarios that favor this tool, no exclusions, and no mention of prerequisites or filters that might condition its use.

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