Fetch public Shop.app reviews for a merchant profile by handle, with optional limit up to 50, to assess customer feedback.
List Shop.app shop reviews. Returns public reviews for a Shop.app merchant profile.
| Name | Required | Description | Default |
|---|---|---|---|
| limit | No | Maximum reviews, defaults to 20 and supports up to 50 | |
| handle | Yes | Shop handle |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must disclose behavioral traits. It only notes 'public reviews' but omits authentication needs, rate limits, pagination, or return format details.
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 no wasted words. The purpose is front-loaded and immediately clear.
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?
Without an output schema, the description should explain what the returned data contains. It only says 'returns public reviews' without field details. Given simplicity, more completeness is needed.
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 covers both parameters (handle, limit) with descriptions. The tool description adds no extra meaning beyond what the schema provides, so baseline 3 is appropriate.
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 the tool lists public reviews for a Shop.app merchant profile, using specific verb 'List' and resource 'shop reviews'. It distinguishes from siblings like shop_app_product_reviews by targeting shop-level reviews.
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 provides no guidance on when to use this tool versus alternative review tools (e.g., shop_app_product_reviews). No exclusions or context for selection are given.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.