Retrieve paginated Target product questions with nested answers by TCIN for product Q&A displays and customer insights.
List Target product questions and answers. Returns paginated product questions with their nested answers.
| Name | Required | Description | Default |
|---|---|---|---|
| page | No | Zero-based page | |
| tcin | Yes | Numeric Target item id | |
| per_page | No | Questions per page |
Changes observed during successful MCP inspections.
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full burden. It discloses pagination and nested answers, which is useful, but does not mention rate limits, data freshness, error behavior, or default pagination values. Adequate but not rich.
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?
Two concise sentences with a clear action verb. Minor redundancy between 'questions and answers' and 'product questions with their nested answers', but overall efficient and 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?
Given the simple list operation and fully described schema, the description provides key return information (paginated, nested answers). It could mention the required tcin parameter or defaults, but these are available in the schema.
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% with each parameter described (page, tcin, per_page). The description adds no extra meaning beyond the schema, so 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 uses a specific verb 'List' with a clear resource 'Target product questions and answers', distinguishing it from sibling target_reviews (reviews) and target_product (product details).
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?
No guidance is provided for when to use this tool versus alternatives like target_reviews or target_product. The description only states what it does without any exclusions, alternatives, or context.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.