Fetch paginated written product reviews for a Target item by numeric TCIN; zero-based paging supports up to page 50.
List Target product reviews. Returns paginated written reviews for a Target item. Pagination is zero-based and page 50 is the upstream maximum.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Zero-based page | |
| tcin | Yes | Numeric Target item id | |
| per_page | No | Reviews per page |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
The description discloses pagination behavior (zero-based and page 50 maximum) which is useful beyond the schema. However, it does not cover other behavioral aspects such as authentication, rate limits, or response field details. Since no annotations are provided, the description carries the transparency burden but remains partial.
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 two sentences that quickly state the purpose and the key pagination detail. There is no filler, redundancy, or unnecessary elaboration, making it highly concise and easy to parse.
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?
The tool is simple with three documented parameters, and the description covers the purpose and pagination constraints effectively. Without an output schema, it does not define what fields a 'written review' contains, which is a minor gap for agents needing to interpret the response, but it is not a blocker for correct invocation.
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 already describes all three parameters with 100% coverage, providing a baseline of 3. The description adds value by specifying the upstream maximum page (50) and reiterating the zero-based pagination, which is critical for correct invocation. It does not mention default values but still enriches the semantic meaning.
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 'List Target product reviews' and further clarifies 'Returns paginated written reviews for a Target item.' This is a specific verb+resource combination that distinguishes it from sibling tools like target_product or target_questions.
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?
The description implies usage through its purpose statement but does not explicitly state when to use this tool versus alternatives. It lacks exclusions or references to sibling tools, leaving the agent to infer selection based on the tool's name and purpose.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.